STINNER Victor added the comment:
The root issue will be solved by bpo-37531: ensure that regrtest kills a worker
process if it takes longer than TIMEOUT seconds.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Fix regrtest timeout for subproces
Jeremy Kloth added the comment:
The test run was stopped by me terminating the stuck processes on the buildbot
worker itself. This happens approximately once a month or so.
As of late, its been stuck in test_concurrent_futures, but it can get stuck in
any test that uses multiprocessing (the
New submission from STINNER Victor :
AMD64 Windows7 SP1 3.7:
https://buildbot.python.org/all/#/builders/130/builds/935
0:23:27 load avg: 7.92 [412/416] test_plistlib passed -- running: test_venv (1
min 26 sec), test_concurrent_futures (23 min 26 sec)
0:23:32 load avg: 7.29 [413/416] test_argpa
