gh-116303: Handle disabled test modules in test.support
Yak shave for gh-116303
(the hypothesis failure has its own issue: #116455)
For the Windows failures, see:
- #116458
- #116467
Marking this as a draft until #116458 has landed.
Marking this as a draft until https://github.com/python/cpython/pull/116458 has landed.
This fix has landed in the main branch.
LGTM.
Thanks, but we cannot merge this; the Windows ~~free-threaded~~ builds still fail :(
- https://github.com/python/cpython/actions/runs/8458383758/job/23172507933?pr=116482
@vstinner, would you like to review the updated PR?
Overall, it's kind of strange to ask (1) to not build tests and (2) to run tests :-)
More specifically, they are asking to not build test extension modules, but still be able to run the test suite. I think it is a legitimate thing to ask :)
Thanks for the reviews; I'm enabling auto-merge.
Thanks @erlend-aasland for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. 🐍🍒⛏🤖
Sorry, @erlend-aasland, I could not cleanly backport this to 3.12 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 6c8ac8a32fd6de1960526561c44bc5603fab0f3e 3.12
Sorry, @erlend-aasland, I could not cleanly backport this to 3.11 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 6c8ac8a32fd6de1960526561c44bc5603fab0f3e 3.11
I'm not so sure about backporting this anymore.
The main reason to backport test changes is to make future backports easier. If there are already conflicts, I wouldn't feel bad about not backporting.