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 aeros
Recipients aeros, eric.snow, vstinner
Date 2020-01-15.05:49:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I also just realized that I can run "test.test__xxsubinterpreters.DestroyTests" by itself with:

./python -m test test__xxsubinterpreters.DestroyTests -j200 -F -v

For some reason, I hadn't thought of running that class of tests by itself to isolate the failure. Prior to this issue, I didn't have experience in debugging a group of intermittent failures occurring across different tests. For most bugs I've worked on so far, it was a single, clearly defined point of failure; or a behavioral issue that wasn't covered in the regression tests.

But, that's certainly useful to know for future debugging and will help to improve my workflow for further investigating this issue. It's a lot more effective than adding a bunch of skip test annotations throughout the test file!
Date User Action Args
2020-01-15 05:49:30aerossetrecipients: + aeros, vstinner, eric.snow
2020-01-15 05:49:30aerossetmessageid: <>
2020-01-15 05:49:30aeroslinkissue37224 messages
2020-01-15 05:49:30aeroscreate