-
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
GH-44389: [Java][Integration][Release] Use Python 3.12 for verify-rc-source-integration-linux-conda-latest-amd64 #44395
Conversation
…fy-rc-source-integration-linux-conda-latest-amd64 Because JPype doesn't support Python 3.13 yet. See also: * apacheGH-44389 * https://discuss.python.org/t/api-for-python-3-13-prevents-use-of-3rd-party-gc-allocators/62709/5
|
@github-actions crossbow submit verify-rc-source--linux- |
Revision: 8a9a6be Submitted crossbow builds: ursacomputing/crossbow @ actions-b9724982b4 |
It seems 3.13 still got installed? |
@github-actions crossbow submit verify-rc-source--linux- |
Revision: 158c136 Submitted crossbow builds: ursacomputing/crossbow @ actions-15b8e1c9d8 |
@jorisvandenbossche any idea why the Python verification has just started failing for the above?
|
@github-actions crossbow submit verify-rc-source-integration-linux-conda-latest-amd64 |
Revision: 22d2412 Submitted crossbow builds: ursacomputing/crossbow @ actions-795491bc3b
|
@github-actions crossbow submit verify-rc-source-integration-linux-conda-latest-amd64 |
Revision: b543a5b Submitted crossbow builds: ursacomputing/crossbow @ actions-9e116399c9
|
@github-actions crossbow submit verify-rc-source--linux- |
This comment was marked as outdated.
This comment was marked as outdated.
Revision: b543a5b Submitted crossbow builds: ursacomputing/crossbow @ actions-e3f57c0557 |
These jobs are from main. Just validating status thereRevision: 27e56f0 Submitted crossbow builds: ursacomputing/crossbow @ verify-rc-source-python-main-1 |
I am really confused, why is the almalinux job, for example, failing here but not on main, when the change here is not on the workflow for the job: https://github.com/ursacomputing/crossbow/actions/runs/11328978008/workflow |
The failed job (that uses my fork) creates https://github.com/ursacomputing/crossbow/actions/runs/11328978008/job/31503426291#step:6:9674
But the succeeded job (that uses apache/arrow) creates https://github.com/ursacomputing/crossbow/actions/runs/11329033094/job/31503611194#step:6:9730
I think that it's caused by my fork doesn't have all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Thanks @kou ! The tag issue makes sense. Thanks for fixing it. I've created RC0 already, I'll merge this for 19.0.0 and will add the backport-candidate
label. If I have to create a new RC I'll add to 18.0.0 just to fix the CI failure.
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit d0e7d07. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 3 possible false positives for unstable benchmarks that are known to sometimes produce them. |
Rationale for this change
Because JPype doesn't support Python 3.13 yet.
See also:
What changes are included in this PR?
Pin Python 3.12.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.