[CI] Only run test_ray_serve for Ray 2.6.0 and later #1288
Merged
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
sihanwang41
approved these changes
Aug 2, 2023
lowang-bh
pushed a commit
to lowang-bh/kuberay
that referenced
this pull request
Sep 24, 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?
Before Ray 2.6.0, there was a bug in Ray Serve that caused the
test_ray_serveto be quite unstable (See #1058 for more details). Therefore, we only runtest_ray_servefor Ray versions 2.6.0 and later. Currently, Ray 2.6.0 is not included in the KubeRay CI pipeline. However, I believe the release manager for Ray 2.6.0 will open a PR to update the version from 2.5.0 to 2.6.0 (or 2.6.2) in the next few days.Related issue number
Closes #1058
Checks
test_ray_serveis executed in Compatibility Test - Nightly.test_ray_serveis skipped in Compatibility Test - 2.5.0