Alexander Kanavin <alex.kana...@gmail.com> added the comment:
I am seeing this one too in my yocto builds of 3.10rc2. What is bizarre is that the issue does not occur if the multiprocessing test is run in isolation: python3 -m test -v test_multiprocessing_fork but quite reliably does occur (three times in three different spots) if the whole test suite is executed: python3 -m test -v ---------- nosy: +Alexander Kanavin _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue45128> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
