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

[CI] [Cluster] Fix example GCP GPU/docker example cluster YAML file #41134

Merged
merged 5 commits into from
Nov 21, 2023

Conversation

architkulkarni
Copy link
Contributor

@architkulkarni architkulkarni commented Nov 14, 2023

Why are these changes needed?

Fixes the broken GCP GPU docker example YAML by updating the image and cuda version. (Thanks @PaulFenton for the fix!)

Adds a release test that checks that ray up works with this YAML file (it didn't work before).

Switched the image used in the YAML to ray instead of ray-ml because ray-ml gave errors with running out of disk space, and because it makes the test run faster. If it's important to make ray-ml the default, we can probably just increase diskSizeGb and test it again.

Related issue number

Closes #35266

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@architkulkarni
Copy link
Contributor Author

Screenshot 2023-11-21 at 8 45 33 AM The release test passed.

@architkulkarni architkulkarni marked this pull request as ready for review November 21, 2023 16:46
@architkulkarni architkulkarni requested review from ericl and a team as code owners November 21, 2023 16:46
@architkulkarni
Copy link
Contributor Author

Linkcheck failure is unrelated, this PR doesn't touch the docs.

@architkulkarni architkulkarni added the tests-ok The tagger certifies test failures are unrelated and assumes personal liability. label Nov 21, 2023
Copy link
Member

@hongchaodeng hongchaodeng left a comment

Choose a reason for hiding this comment

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

LGTM!

@architkulkarni architkulkarni merged commit a1a9a48 into ray-project:master Nov 21, 2023
16 of 18 checks passed
ujjawal-khare pushed a commit to ujjawal-khare-27/ray that referenced this pull request Nov 29, 2023
…ay-project#41134)

Fixes the broken GCP GPU docker example YAML by updating the image and cuda version. (Thanks @PaulFenton for the fix!)

Adds a release test that checks that ray up works with this YAML file (it didn't work before).

Switched the image used in the YAML to ray instead of ray-ml because ray-ml gave errors with running out of disk space, and because it makes the test run faster. If it's important to make ray-ml the default, we can probably just increase diskSizeGb and test it again.

Related issue number
Closes ray-project#35266

---------

Signed-off-by: Archit Kulkarni <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests-ok The tagger certifies test failures are unrelated and assumes personal liability.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Cluster launcher] GCP example-gpu-docker.yaml fails setup commands waiting for nvidia-smi
3 participants