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

[Tests][BugFix] Fix invalid YAML in SkyServe smoke test w/ autoscaling #3399

Closed
wants to merge 2 commits into from

Conversation

cblmemo
Copy link
Collaborator

@cblmemo cblmemo commented Apr 1, 2024

In #3361 we introduced new checks for the service YAML, which caused several of our smoke test failures. This PR fixes the bug.

Tested (run the relevant ones):

  • Code formatting: bash format.sh
  • Any manual or new tests for this PR (please specify below)
    • Manually sky serve up every YAML in tests/skyserve folder and make sure it works
  • All smoke tests: pytest tests/test_smoke.py
  • Relevant individual smoke tests: pytest tests/test_smoke.py::test_fill_in_the_name
    • tests/test_smoke.py::test_skyserve_dynamic_ondemand_fallback
    • tests/test_smoke.py::test_skyserve_base_ondemand_fallback
  • Backward compatibility tests: bash tests/backward_comaptibility_tests.sh

@@ -6,6 +6,7 @@ service:
min_replicas: 2
max_replicas: 3
base_ondemand_fallback_replicas: 1
target_qps_per_replica: 1
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should this be 1 or larger value? We don't expect it to scale up during the test.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

SG

@cblmemo
Copy link
Collaborator Author

cblmemo commented Apr 7, 2024

Closed since already fixed.

@cblmemo cblmemo closed this Apr 7, 2024
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.

3 participants