Bug report

Bug description:

See the logs in https://buildbot.python.org/all/#/builders/1138/builds/498

10 slowest tests:
- test.test_multiprocessing_spawn.test_threads: 10 min 14 sec
- test.test_multiprocessing_fork.test_threads: 10 min 13 sec
- test_imaplib: 1 min 31 sec
- test_signal: 1 min 18 sec
- test.test_multiprocessing_spawn.test_processes: 52.6 sec
- test.test_concurrent_futures.test_wait: 48.6 sec
- test_socket: 40.7 sec
- test.test_multiprocessing_forkserver.test_processes: 40.1 sec
- test_io: 37.4 sec
- test_codecs: 37.3 sec

Normally those two .test_threads sub-suites in test_multiprocessing do not make the top 10 slowest at all.

Something odd is going on and occasionally making them sit around for a very long time before apparently succeeding anyways. I've seen it multiple time in the rpi buildbot logs. I expect it'll show up on some other bots as well but I haven't gone hunting.

CPython versions tested on:

3.12

Operating systems tested on:

Linux

Linked PRs

• gh-113205: test_multiprocessing.test_terminate: Test the API on threadpools #114186
• [3.12] gh-113205: test_multiprocessing.test_terminate: Test the API on threadpools (GH-114186) #114222
• [3.11] gh-113205: test_multiprocessing.test_terminate: Test the API on threadpools (GH-114186) #114223
• gh-113205: test_multiprocessing.test_terminate: Give tasks a chance to start #114249
• [3.12] gh-113205: test_multiprocessing.test_terminate: Give tasks a chance to start (GH-114249) #114516
• [3.11] gh-113205: test_multiprocessing.test_terminate: Give tasks a chance to start (GH-114249) #114517