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

Upstream CI build failing due to pyarrow install #9654

Closed
jrbourbeau opened this issue Nov 14, 2022 · 1 comment · Fixed by #9655
Closed

Upstream CI build failing due to pyarrow install #9654

jrbourbeau opened this issue Nov 14, 2022 · 1 comment · Fixed by #9655
Labels
tests Unit tests and/or continuous integration upstream

Comments

@jrbourbeau
Copy link
Member

I noticed our upstream build is failing with

Run source continuous_integration/scripts/install.sh
++ [[ -n 1 ]]
++ arr=($(mamba search --override-channels -c arrow-nightlies pyarrow | tail -n 1))
+++ mamba search --override-channels -c arrow-nightlies pyarrow
+++ tail -n 1
++ export PYARROW_VERSION=11.0.0.dev84
++ PYARROW_VERSION=11.0.0.dev84
++ mamba install -y -c arrow-nightlies pyarrow=11.0.0.dev84
conda-forge/linux-64                                        Using cache
conda-forge/noarch                                          Using cache

Looking for: ['pyarrow=11.0.0.dev84']


Pinned packages:
  - python 3.9.*


Encountered problems while solving:
  - package pyarrow-11.0.0.dev84-py310hbc2c91e_0_cuda requires python >=3.10,<3.11.0a0, but none of the providers can be installed

Looking at https://anaconda.org/arrow-nightlies/pyarrow/files, it appears pyarrow nightlies might have recently switched to Python 3.10 only?

cc @jorisvandenbossche @charlesbluca

@jrbourbeau jrbourbeau added tests Unit tests and/or continuous integration upstream labels Nov 14, 2022
@jrbourbeau
Copy link
Member Author

Trying Python 3.10 over in #9655

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Unit tests and/or continuous integration upstream
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant