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

unpin pyarrow for windows #42097

Merged
merged 2 commits into from
Jan 25, 2024
Merged

unpin pyarrow for windows #42097

merged 2 commits into from
Jan 25, 2024

Conversation

mattip
Copy link
Contributor

@mattip mattip commented Dec 26, 2023

Why are these changes needed?

Toward fixing #38300

PR #29993 added a local ray fix for issue apache/arrow#26685, but at the time windows failed the tests with pyarrow7. In issue #38300 the suggested fix was

  • release the pin
  • add a version check when serializing a pyarrow dataset
  • Handle any remaining behavior gap related to _register_arrow_data_serializer(), and include an environment variable to override the Pyarrow version check

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 :(

@mattip
Copy link
Contributor Author

mattip commented Dec 26, 2023

step 1: release the pin. Let's see what tests fail?

@mattip
Copy link
Contributor Author

mattip commented Dec 26, 2023

I also ran the test added in #29993 locally and it passed.

@mattip
Copy link
Contributor Author

mattip commented Jan 22, 2024

cc @anyscalesam

@mattip
Copy link
Contributor Author

mattip commented Jan 22, 2024

I think releasing the pin is enough to solve the issue.

@mattip
Copy link
Contributor Author

mattip commented Jan 25, 2024

I don't think the CI failure is related. It would be nice to get some eyes on this.

@edoakes
Copy link
Contributor

edoakes commented Jan 25, 2024

CI failure is likely unrelated. Updating branch to re-run

@scottjlee
Copy link
Contributor

scottjlee commented Jan 25, 2024

Contents of PR LGTM - I triggered a postmerge test to see how things look on windows tests.
https://buildkite.com/ray-project/postmerge/builds/2689

Copy link
Contributor

@scottjlee scottjlee left a comment

Choose a reason for hiding this comment

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

LGTM, @c21 to approve and merge

@edoakes edoakes merged commit 68bd737 into ray-project:master Jan 25, 2024
9 checks passed
khluu pushed a commit that referenced this pull request Jan 27, 2024
Toward fixing #38300

PR #29993 added a local ray fix for issue apache/arrow#26685, but at the time windows failed the tests with pyarrow7. In issue #38300 the suggested fix was to release the pin.

Signed-off-by: mattip <[email protected]>
Co-authored-by: Edward Oakes <[email protected]>
Signed-off-by: khluu <[email protected]>
@RocketRider
Copy link
Contributor

Could we pick that for 2.9.2?

@tonyhoo
Copy link

tonyhoo commented Feb 29, 2024

When will this fix be released. It introduced installation issue for AutoGluon on Windows platform with Python 3.11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants