Repository navigation
CI: add cp314/cp314t nighly wheel builds - #23187
Conversation
|
Hmm, the one wheel build failure here, for The exact same job passed on my fork an hour earlier. All the relevant packages seem to be identical: Normally |
|
Failed again at the same point - back to debugging on fork. |
|
Re-ran it for a third time with debug logging enabled. It failed even earlier, on a different Re-ran again as well on my own fork, and the build passed: CI log. This is very mysterious. |
Follow up on this later, likely one or more issues in CPython, NumPy, and/or Pythran. The aarch64 job was hanging at various places in the test suite. The x86-64 job was failing on `pythran` generation .cpp code at build time, repeatedly and on multiple source files.
|
Skipping the second |
|
This is good to merge now. The one failure in a non-wheel job is unrelated. |
This reverts changes made in scipy#23187, keeping the commented out code for once 3.15-dev arrives.
This reverts changes made in scipy#23187, keeping the commented out code for once 3.15-dev arrives. [ci skip]
This reverts changes made in scipy#23187, keeping the commented out code for once 3.15-dev arrives. [ci skip]
We're about 5-6 weeks away from needing to do a release with Python 3.14 support (see the release schedule in PEP 745), so it'll be good to enable nightly wheels now and fix/report issues.
There are a couple of tests that needed skipping - issues filed for those: gh-23172, gh-23185. Also, there is one wheel (
cp314t-musllinux_1_2_aarch64) for which the test suite is hanging. The hang is the most serious problem and needs investigating next. That wheel is probably the least critical of all wheels though, so it's best to get the other ones deployed now.We shouldn't backport this PR just yet; once 3.14.0rc1 is out and numpy has done a release that supports it, this will be significantly simpler to support on the
maintenance/1.16.xbranch.