➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Johan Dahlin, db3l, emilyemorehouse, eric.snow, koobs, nascheme, ncoghlan, pmpp, serhiy.storchaka, shprotx, steve.dower, vstinner, yselivanov
Date 2019-06-03.16:23:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559579000.5.0.722072175899.issue33608@roundup.psfhosted.org>
In-reply-to
Content 
What annoy me the most in this issue is that I am unable to reproduce it. Even directly on the FreeBSD CURRENT buildbot, I failed to reproduce rhe crash even when I stressed the buildbot and the test.

On the other side, when the CI runs the test suite, crashes are likely!?

These bugs are the worst.

IMHO we must make multiprocessing more deterministic. Python 3.8 is better, but there are still many known issues.
https://pythondev.readthedocs.io/unstable_tests.html

test_venv multiprocessing test misuses the multiprocessing issue, it emirs a ResourceWarning.
History
Date User Action Args
2019-06-03 16:23:20vstinnersetrecipients: + vstinner, nascheme, db3l, ncoghlan, pmpp, eric.snow, serhiy.storchaka, yselivanov, koobs, steve.dower, emilyemorehouse, Johan Dahlin, shprotx
2019-06-03 16:23:20vstinnersetmessageid: <1559579000.5.0.722072175899.issue33608@roundup.psfhosted.org>
2019-06-03 16:23:20vstinnerlinkissue33608 messages
2019-06-03 16:23:20vstinnercreate