New submission from STINNER Victor <vstin...@python.org>:
Sadly, faulthandler failed to dump the Python traceback and kill the process. Instead, the main libregrtest process had to kill the child process (process group) :-( https://buildbot.python.org/all/#/builders/152/builds/420 ... 0:56:25 load avg: 0.22 running: test_multiprocessing_fork (35 min 42 sec) 0:56:55 load avg: 0.40 running: test_multiprocessing_fork (36 min 12 sec) 0:57:25 load avg: 0.24 running: test_multiprocessing_fork (36 min 42 sec) 0:57:55 load avg: 0.25 running: test_multiprocessing_fork (37 min 12 sec) Kill <TestWorkerProcess #4 running test=test_multiprocessing_fork pid=58534 time=37 min 30 sec> process group 0:58:13 load avg: 0.24 [420/420/3] test_multiprocessing_fork timed out (37 min 30 sec) (37 min 30 sec) See also bpo-39995: test_concurrent_futures.test_ressources_gced_in_workers() timed out after 15 minutes on AMD64 Ubuntu Shared 3.x. ---------- components: Tests messages: 364464 nosy: koobs, vstinner priority: normal severity: normal status: open title: test_multiprocessing_fork hangs on AMD64 FreeBSD Shared 3.x versions: Python 3.9 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue39996> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
