[cluster-launcher] Pick GCP cluster launcher tests and fix #37797
Conversation
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
…y-project#37680) Why are these changes needed? Add release test that both check the cluster is alive, as well as the number of (autoscaled) nodes are expected.
…y-project#37718) --------- Signed-off-by: rickyyx <rickyx@anyscale.com>
rickyyx
requested review from
wuisawesome,
DmitriGekhtman,
ericl and
a team
as code owners
|
This is to fix a GCP cluster launcher issue we discovered that was introduced in 2.5.0 cc @zhe-thoughts |
zhe-thoughts
approved these changes
Jul 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why are these changes needed?
This PR has two commits:
Related issue number
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.