Skip to content

Reenable the Cygwin build test when Cygwin support Python 3.12 #26247

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

Open
charris opened this issue Apr 9, 2024 · 1 comment
Open

Reenable the Cygwin build test when Cygwin support Python 3.12 #26247

charris opened this issue Apr 9, 2024 · 1 comment

Comments

@charris
Copy link
Member

charris commented Apr 9, 2024

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.

@DWesl
Copy link
Contributor

DWesl commented Mar 5, 2025

Updates on progress: Cygwin now has a Python 3.12 test package, with corresponding NumPy 2.2 test package.

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants