-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-40112: [CI][Python] Ensure CPython is selected, not PyPy #40131
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
Conversation
Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios.
|
@github-actions crossbow submit test-conda-* |
This comment was marked as outdated.
This comment was marked as outdated.
|
@pitrou I pushed a fix. Annoying that you need to use a different wildcard :( @github-actions crossbow submit test-conda-* |
|
@github-actions crossbow submit test-conda-* |
|
Revision: 1566fdb Submitted crossbow builds: ursacomputing/crossbow @ actions-bcdf91a90b |
|
Thanks for the fix @xhochy . I'll merge this in the interest of improving CI results. |
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit ec3723e. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios. * Closes: #40112 Lead-authored-by: Antoine Pitrou <antoine@python.org> Co-authored-by: Uwe L. Korn <uwe.korn@quantco.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios. * Closes: #40112 Lead-authored-by: Antoine Pitrou <antoine@python.org> Co-authored-by: Uwe L. Korn <uwe.korn@quantco.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
Sometimes, mamba might select PyPy over CPython in certain environment upgrade/downgrade scenarios.