-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Pin Redis version to < 4.0.0 #20430
Pin Redis version to < 4.0.0 #20430
Conversation
Dups Kai's fix. |
@ericl this is is intended for testing windows breakage, which is a separate issue. |
We actually need to merge this short term to fix |
Hiredis doesn't have M1-mac precompiled wheels, so we pin-down the redis version to avoid breaking m1 while fixing the test breakage. |
@pcmoritz this doesn't solve windows breakge https://github.com/ray-project/ray/runs/4228283679?check_suite_focus=true#step:8:1555 |
Yeah I saw :(. The windows breakage does look very redis related though. Could something else have been upgraded related to redis? |
<!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? This pin is needed to fix `test_output` on master, which broke when 4.0.0 was released. It may also fix the windows build (unsure). ## Related issue number <!-- For example: "Closes #1234" --> ## Checks - [ ] 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 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 :(
<!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? This pin is needed to fix `test_output` on master, which broke when 4.0.0 was released. It may also fix the windows build (unsure). ## Related issue number <!-- For example: "Closes #1234" --> ## Checks - [ ] 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 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 :(
Why are these changes needed?
This pin is needed to fix
test_output
on master, which broke when 4.0.0 was released.It may also fix the windows build (unsure).
Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.