Skip to content

CI: green builds #39541

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
jreback opened this issue Feb 1, 2021 · 2 comments · Fixed by #39544
Closed

CI: green builds #39541

jreback opened this issue Feb 1, 2021 · 2 comments · Fixed by #39544
Labels
CI Continuous Integration Dependencies Required and optional dependencies
Milestone

Comments

@jreback
Copy link
Contributor

jreback commented Feb 1, 2021

so the confluence of some pyarrow pinning and release of numpy 1.20 are causing pain rn. several PRs have addressed most of these. I think 38_locale is the remaining problem, needs to pin pyarrow.

We need to get to green on master & 1.2.2 before any other PRs.

cc @pandas-dev/pandas-core

@jreback jreback added CI Continuous Integration Dependencies Required and optional dependencies labels Feb 1, 2021
@jreback jreback added this to the 1.2.2 milestone Feb 1, 2021
@jbrockmendel jbrockmendel mentioned this issue Feb 1, 2021
4 tasks
@MarcoGorelli
Copy link
Member

MarcoGorelli commented Feb 1, 2021

before any other PRs.

I read this after having merged #39500, though that was only a simple doc change - sorry about that, won't do any more til it's all green again

@jorisvandenbossche
Copy link
Member

The reason it was failing because 1) we were pinning to pyarrow 1.0.0, and only 1.0.1 was rebuilt on conda-forge to be compatible with numpy 1.20, and 2) pyarrow 0.17 was also not rebuilt, which is done now, but I think it is fine to keep the pin to an older numpy version on that CI build.

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

Successfully merging a pull request may close this issue.

3 participants