[Post Ray 2.8.0 Release] Update Ray versions to Ray 2.8.0 #1678
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
architkulkarni
approved these changes
Nov 22, 2023
4 tasks
architkulkarni
added a commit
that referenced
this pull request
Dec 28, 2023
As part of the 2.9.0 release, this PR updates the latest Ray version used in the KubeRay repo to 2.9.0. Example PR: #1678 We only test the three most recent Ray versions in e2e tests. We unskip a test that was skipped due to [Core][GCS FT] Raylet on the worker node crashes unexpectedly when head crashes ray#41343, which is fixed in Ray 2.9.0. Update the serve e2e test example to remove DAGDriver, which was removed completely in Ray 2.9.0 (Thanks @zcin !) --------- Signed-off-by: Archit Kulkarni <architkulkarni@users.noreply.github.com> Signed-off-by: cindyz <cindyz@anyscale.com> Co-authored-by: cindyz <cindyz@anyscale.com>
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?
The Ray 2.8 release manager may forget to do this. This is important for locating the compatibility issues, such as ray-project/ray#41343, between Ray & KubeRay.
Related issue number
Checks