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.
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] fix smoke test race condition on first run #4494
base: master
Are you sure you want to change the base?
[Tests] fix smoke test race condition on first run #4494
Changes from 3 commits
2a0929b
ba0fe3a
d6faacd
096e59a
344a5db
77065be
4635d84
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we still need the comment here? The
logger.fatal
statement below is quite clear.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.
Good catch, removed the log for simplicity~
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.
How about we use the same
handle_boto_error
here as well to keep the error handling consistent and raise the sameexc
error?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.
IIUC,
boto error
is specific to the errors returned by AWS boto3 SDK, simulating a boto error here adding extra indirections. Besides,handle_boto_error
will prefix error message withBoto3 error:
, which looks misleading, wdyt?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.
Makes sense. I was referring to raising the error from the caller directly, but I am ok with a custom exception.
If we are raising
SystemExit
here, it might cause the whole system to exit as we don't catch the system exit explicitly.https://github.com/skypilot-org/skypilot/blob/master/sky/provision/provisioner.py#L136-L197
Just a note, we decide the failover across clouds based on the error message here: https://github.com/skypilot-org/skypilot/blob/master/sky/backends/cloud_vm_ray_backend.py#L1119-L1137. I assume if we fail in this case, we should skip the whole AWS cloud.