Skip to content

CI: pin some builds to use pyarrow==1.0 #37306

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

Closed
jorisvandenbossche opened this issue Oct 21, 2020 · 3 comments · Fixed by #37822
Closed

CI: pin some builds to use pyarrow==1.0 #37306

jorisvandenbossche opened this issue Oct 21, 2020 · 3 comments · Fixed by #37822
Labels
CI Continuous Integration
Milestone

Comments

@jorisvandenbossche
Copy link
Member

Now that pyarrow 2.0 is released, it will get picked by the CI builds that don't pin the pyarrow version. It would be good to pin some builds to use pyarrow 1.0.

See this overview table of @simonjayhawkins at #35259 (comment)

@dsaxton
Copy link
Member

dsaxton commented Oct 21, 2020

What's the best way to figure out which ones need to be pinned? See what starts failing and then pin as needed, or is there a smarter way to do this?

@jorisvandenbossche
Copy link
Member Author

I don't think it needs to be based on what is failing (because all builds should be passing right now?). Based on the table at #35259 (comment), there are now 4 envs that have 1.0. We could for example leave 2 of them at "latest version", and pin 2 (or 1) of them to pyarrow 1.0 ?

@simonjayhawkins
Copy link
Member

I guess we could also maybe consider adding the nightly build of PyArrow to np-dev

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

Successfully merging a pull request may close this issue.

3 participants