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
{{ message }}
Repository navigation
test_concurrent_futures stopped after 25 hours on AMD64 Windows7 SP1 3.7 #81494
Activity
vstinner commentedon Jun 17, 2019
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_argparse passed -- running: test_venv (1 min 31 sec), test_concurrent_futures (23 min 31 sec)
0:23:34 load avg: 7.29 [414/416] test_venv passed (1 min 32 sec) -- running: test_concurrent_futures (23 min 32 sec)
0:23:37 load avg: 6.71 [415/416] test_largefile passed -- running: test_concurrent_futures (23 min 35 sec)
running: test_concurrent_futures (24 min 6 sec)
running: test_concurrent_futures (24 min 36 sec)
...
running: test_concurrent_futures (25 hour 25 min)
running: test_concurrent_futures (25 hour 26 min)
running: test_concurrent_futures (25 hour 26 min)
running: test_concurrent_futures (25 hour 27 min)
running: test_concurrent_futures (25 hour 27 min)
running: test_concurrent_futures (25 hour 28 min)
program finished with exit code 1
elapsedTime=91968.468000
jkloth commentedon Jun 17, 2019
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 spawned pool never terminates).
vstinner commentedon Jul 29, 2019
The root issue will be solved by bpo-37531: ensure that regrtest kills a worker process if it takes longer than TIMEOUT seconds.