[chore] upgrade Ray to 2.46.0 in remaining places #3724
Merged
Conversation
This file contains hidden or 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
follow-up to ray-project#3547 Signed-off-by: David Xia <david@davidxia.com>
from 1G. Otherwise, tests like TestCreateJobSubmission fail because the head Contiainer is OOMKilled. Seems like the newer Ray 2.46.0 uses more memory in the head. Signed-off-by: David Xia <david@davidxia.com>
|
all checks have passed, ready for review. I wonder if some of the e2e tests (like for apiserver and ray-operator, see second commit) have gotten flakier as a result? I don't have a sense of how often these e2e tests flake in master branch. Is there a flaky test tracker with historical data? |
There was a problem hiding this comment.
Pull Request Overview
This PR upgrades the Ray version references across multiple configuration and test files to version 2.46.0, ensuring consistency throughout the project.
- Updated Docker image tags and Ray version strings in benchmark, API server, and e2e test configurations.
- Aligned the version across both YAML configurations and Makefile variables.
Reviewed Changes
Copilot reviewed 49 out of 49 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| benchmark/perf-tests/1000-rayjob/config.yaml | Updated image tag to ray:2.46.0. |
| benchmark/perf-tests/1000-raycluster/raycluster.yaml | Updated rayVersion to 2.46.0. |
| benchmark/perf-tests/1000-raycluster/config.yaml | Updated image tag to ray:2.46.0. |
| benchmark/perf-tests/100-rayjob/ray-data-image-resize.yaml | Updated rayVersion to 2.46.0. |
| benchmark/perf-tests/100-rayjob/pytorch-mnist-rayjob.yaml | Updated rayVersion to 2.46.0. |
| benchmark/perf-tests/100-rayjob/config.yaml | Updated image tag to ray:2.46.0. |
| benchmark/perf-tests/100-raycluster/raycluster.yaml | Updated image tags to ray:2.46.0. |
| benchmark/memory_benchmark/scripts/ray-cluster.benchmark.yaml.template | Updated rayVersion and image tag to 2.46.0. |
| apiserver/test/service/serviceV2 | Updated image tag to ray:2.46.0-py310. |
| apiserver/test/service/serviceV1 | Updated image tag to ray:2.46.0-py310. |
| apiserver/test/job/query | Updated image tag to ray:2.46.0-py310. |
| apiserver/test/job/job | Updated image tag to ray:2.46.0-py310. |
| apiserver/test/e2e/utils.go | Increased memory constant from 1 to 4. |
| apiserver/test/e2e/defaults.go | Updated RayVersion and RayImage to 2.46.0. |
| apiserver/test/e2e/apiserversdk/constants.go | Updated RayImage to 2.46.0. |
| apiserver/test/cluster/cluster_external_redis.yaml | Updated rayVersion and image to 2.46.0. |
| apiserver/test/cluster/cluster/cluster | Updated image tag to ray:2.46.0-py310. |
| apiserver/Makefile | Updated E2E_API_SERVER_RAY_IMAGE variable to ray:2.46.0-py310 and its arm64 variant. |
| apiserver/HttpRequestSpec.md | Updated version and image tags to 2.46.0 and 2.46.0-py310 respectively. |
| apiserver/DEVELOPMENT.md | Updated E2E_API_SERVER_RAY_IMAGE documentation to 2.46.0-py310. |
MortalHappiness
approved these changes
Jun 3, 2025
4 tasks
kevin85421
approved these changes
Jun 3, 2025
pawelpaszki
pushed a commit
to opendatahub-io/kuberay
that referenced
this pull request
Jun 10, 2025
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.
follow-up to #3547
Checks