Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

more fix of smoke tests #4548

Merged
merged 80 commits into from
Jan 24, 2025

Conversation

zpoint
Copy link
Collaborator

@zpoint zpoint commented Jan 9, 2025

  • fix smoke tests bug #4492 is a prerequisite. Review and merge that PR first, then proceed to review this PR.
  • sky serve tests fix
  • separate the serve tests based on parameters to different buildkite agent, example: separate test_skyserve_new_autoscaler_update[rolling] and test_skyserve_new_autoscaler_update[blue_green]
  • Align the buildkite command with pytest: now use args to pass the command transparently to pytest, example:
    • /somke-test --aws
    • /somke-test --managed-jobs --aws
    • /somke-test --serve
    • /somke-test --aws -k test_nonexistent_bucket

^ The last one use -k filter to only trigger test name contains: test_nonexistent_bucket, we can trigger one test with -k option

Test

PYTHONPATH=$(pwd)/tests:$PYTHONPATH \
pytest -n 0 --dist no .buildkite/test_buildkite_pipeline_generation.py
.
9 passed, 2 warnings in 140.30s (0:02:20)

Tested (run the relevant ones):

  • Code formatting: bash format.sh
  • Any manual or new tests for this PR (please specify below)
  • All smoke tests: pytest tests/test_smoke.py
  • Relevant individual smoke tests: pytest tests/test_smoke.py::test_fill_in_the_name
  • Backward compatibility tests: conda deactivate; bash -i tests/backward_compatibility_tests.sh

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 9, 2025

/smoke-tests

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 23, 2025

/smoke-test -k test_managed_jobs_basic

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 23, 2025

/smoke-test -k test_managed_jobs_storage --azure

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 23, 2025

/smoke-test

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 23, 2025

/smoke-test --kubernetes

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 23, 2025

/smoke-test

@Michaelvll Michaelvll added this to the v0.8.0 milestone Jan 23, 2025
.buildkite/generate_pipeline.py Outdated Show resolved Hide resolved
.buildkite/generate_pipeline.py Outdated Show resolved Hide resolved
.buildkite/generate_pipeline.py Outdated Show resolved Hide resolved
tests/smoke_tests/test_mount_and_storage.py Show resolved Hide resolved
tests/smoke_tests/test_managed_job.py Outdated Show resolved Hide resolved
tests/smoke_tests/smoke_tests_utils.py Outdated Show resolved Hide resolved
@@ -43,7 +42,7 @@
# when the controller being on Azure, which takes a long time for launching
# step.
@pytest.mark.managed_jobs
def test_managed_jobs(generic_cloud: str):
def test_managed_jobs_basic(generic_cloud: str):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need this rename?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are many test_managed_jobs_xxx. Rename this function to a unique name so that it is easier to filter using -k if I want to trigger only this test.

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 23, 2025

/smoke-test

@zpoint zpoint requested a review from Michaelvll January 23, 2025 10:32
Copy link
Collaborator

@Michaelvll Michaelvll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @zpoint! LGTM


parsed_args = parser.parse_args(args)

# Collect chosen clouds from the flags
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a TODO for keeping the following sync with the conftest, or do we want to reuse the one in conftest?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I can get the default cloud from conftest, but we still need to do after processing to get the final default cloud for us. Due to our resource limits—for example, we only allow AWS, Azure, GCP, and Kubernetes tests—while the clouds from conftest can include Runpod, IBM, or whatever the user provides. Still, it's good to retrieve as much as possible from conftest.

I'll leave this as a TODO since the current PR already includes many tests. I'll address this in a following PR.

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 24, 2025

/smoke-test -k test_managed_jobs_storage --azure

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 24, 2025

/smoke-test -k test_managed_jobs_storage --azure

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 24, 2025

/quicktest-core

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 24, 2025

/quicktest-core --azure

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 24, 2025

/smoke-test --serve

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 24, 2025

/smoke-test --managed-jobs

@zpoint
Copy link
Collaborator Author

zpoint commented Jan 24, 2025

/smoke-test --managed-jobs --gcp

@zpoint zpoint merged commit 1c94d0f into skypilot-org:master Jan 24, 2025
19 of 20 checks passed
@zpoint
Copy link
Collaborator Author

zpoint commented Jan 24, 2025

Buildkite comment format updated to align with the local pytest format. cc @cblmemo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants