STINNER Victor <vstin...@redhat.com> added the comment:
The bug is still alive: https://buildbot.python.org/all/#/builders/168/builds/294 I found a bug using attached mp_debug.patch. I wrote PR 10755 to try to fix it. I have access to FreeBSD CURRENT buildbot. I only reproduced the bug once using: ./python -m test -v test_multiprocessing_fork -m WithThreadsTestPool --fail-env-changed -F I ran this command 4 times in parallel in 4 terminals, but I failed to reliably reproduce the bug. Even if I stress the computer using "./python -m test -j4 -r" run in different shell, or using my "system_load.py 3" script, I fail to trigger the bug. ---------- keywords: +patch resolution: out of date -> status: closed -> open Added file: https://bugs.python.org/file47953/mp_debug.patch _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33676> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
