You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cygwin currently supports Python 3.9, which we are dropping in Numpy 2.1, so the test has been disabled. The next Python Cygwin plans to support is 3.12, so wait until that release to reenable.
The test can be enabled by going to actions, selecting the cygwin action, and hitting the ... button to get the options.
The text was updated successfully, but these errors were encountered:
The Python threading tests (python -m test.test_threading) fail somewhere in tear-down, in situations where they should be calling either a thread-exit function or a process-exit function. My guess is that it's somehow skipping both, leading to a return from pthread_exit, which very shortly leads to a segfault when it runs out of stack. I have not managed to reproduce this in C, and will likely step through pthread_exit with gdb when I have a bit of time to see how it returns.
DWesl#68 tries to run the NumPy tests anyway, and fails (usually in tests that check threading).
Cygwin currently supports Python 3.9, which we are dropping in Numpy 2.1, so the test has been disabled. The next Python Cygwin plans to support is 3.12, so wait until that release to reenable.
The test can be enabled by going to
actions
, selecting the cygwin action, and hitting the...
button to get the options.The text was updated successfully, but these errors were encountered: