-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[CI][Packaging] Python 3.9 conda builds fail to install GCS testbench #40112
Comments
It looks like there was previously a similar issue with Python 3.11 #33352. I also see the same problem appearing in builds where conda stuff was not modified https://github.com/apache/arrow/actions/runs/7951551953/job/21705115595?pr=40119 |
I think I found a fix by restricting the version of |
Is a bug reported upstream for this? |
Sam questions from me in #40120 (comment)
Happy to fix this so that you don't need a workaround here, but I need a good reason for it. |
I can't find any upstream bug report. I also have not reproduced yet outside of |
I have no idea why |
Ok, here is the reason: PyPy is being installed by mamba instead of CPython!
|
(WTF) |
mamba log:
|
If There must be a problem with dependencies on |
Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios.
Ok, I've opened #40131 with that suggestion. |
@xhochy It does not work:
|
Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios. * Closes: #40112 Lead-authored-by: Antoine Pitrou <[email protected]> Co-authored-by: Uwe L. Korn <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios. * Closes: #40112 Lead-authored-by: Antoine Pitrou <[email protected]> Co-authored-by: Uwe L. Korn <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios. * Closes: #40112 Lead-authored-by: Antoine Pitrou <[email protected]> Co-authored-by: Uwe L. Korn <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
…ache#40131) Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios. * Closes: apache#40112 Lead-authored-by: Antoine Pitrou <[email protected]> Co-authored-by: Uwe L. Korn <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
…ache#40131) Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios. * Closes: apache#40112 Lead-authored-by: Antoine Pitrou <[email protected]> Co-authored-by: Uwe L. Korn <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
Example failure: https://github.com/apache/arrow/actions/runs/7943013070/job/21686899595?pr=40080
This is on a branch but the failure is reproducible on
main
with(I'm sure there is an
archery
command that is equivalent to this but I don't know what it is)This failure is during the docker build step, so if it is completed successfully once I believe CI will cache it and keep returning that result. Without a cache to rely on I can reproduce this locally from
main
(91bf1c9c170c1917ad47bb0dbb38aa5c9fbbbfb2
).To be precise the error actually comes from
pip install grpcio==1.59.0
which is a dependency of GCS testbench https://github.com/googleapis/storage-testbench/blob/43a1a82c39f6349598ec2b77f19cc336eca4ae58/setup.py#L46C10-L46C24Component(s)
Continuous Integration
The text was updated successfully, but these errors were encountered: