Repository navigation
TST: add 3.15t win32 CI and fix issues seen in that build (#31607) - #31671
Merged
Merged
Conversation
Co-authored-by: Charles Harris <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #31607.
Adds win32 3.15t CI and fixes issues seen in the numpy-release automation. I also enabled "full" tests using the same test command as the windows wheel builder.
The Cython issues were reported upstream in cython/cython#7742 and will be fixed in the next Cython release.
I adjusted tests that run meson to use a new helper that embeds debug info into the pytest failure message. That way debug output is no longer swallowed by pytest-xdist and we'll see errors in CI.
Fixed an issue in the cython tests that led to file paths longer than MAX_PATH so I updated the tests to copy the build tree to generate shorter paths.
Disabled
test_dirichlet_moderately_small_alphaon 32 bit builds. 458 MiB is almost 10% of a 32 bit address space and on a test runner with 4 workers it's possible or even likely for memory to get sufficiently fragmented such that this test triggers OOM errors. mimalloc and the free-threaded build might make this situation worse?ping @seberg @charris since this got reasonably involved.
I used Claude Fable 5 to help with this PR.