-
Notifications
You must be signed in to change notification settings - Fork 532
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
[SkyServe][Test] Fix test_smoke.py::test_skyserve_new_autoscaler_update #3824
Merged
Michaelvll
merged 8 commits into
skypilot-org:master
from
landscapepainter:fix_test_skyserve_new_autoscaler_update
Aug 18, 2024
Merged
Changes from 3 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
63611a2
fix test_smoke.py::test_skyserve_new_autoscaler_update
landscapepainter 5fe603a
nit
landscapepainter 93fbd38
format
landscapepainter eed43e4
move out the comment from run at new_autoscaler_after.yaml
landscapepainter 58f34e3
revert comment
landscapepainter 1789432
revert templating
landscapepainter 8bc1c40
nit
landscapepainter ad1f941
nit
landscapepainter File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,10 +5,10 @@ service: | |
replicas: 2 | ||
|
||
resources: | ||
cloud: gcp | ||
cloud: {{generic_cloud}} | ||
ports: 8081 | ||
cpus: 2+ | ||
|
||
workdir: examples/serve/http_server | ||
|
||
run: python3 server.py | ||
run: python3 server.py --port 8081 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch! Is the other changes in this PR needed except for this one? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The test will work by only keeping this change. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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 templating stuff considering we have the
--cloud
in our test already?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even though the test yaml with
cloud: gcp
worked as we expected due to--cloud
option, it was confusing and I was not able to come up with a good reason to keep it ascloud: gcp
while it is being tested for other clouds as well. Should we keep it as it was without templating?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep the original way or just remove the
cloud:
in the YAML, as it seems unnecessary to do a template when ourCLIs
are built for being able to override the fields.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the
cloud:
from YAML, and reverted the template :)