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 db3l
Recipients Bruno Oliveira, Carl.Friedrich.Bolz, Daniel Lepage, Dennis Sweeney, Jim Fasarakis-Hilliard, db3l, gregory.p.smith, iritkatriel, louielu, lukasz.langa, miss-islington, pablogsal, r.david.murray, serhiy.storchaka
Date 2021-11-14.18:56:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
So I'm guessing something is just borderline under 3.9 on Windows.

In some manual testing with a standalone build of 3.9 so far for me:
  -m test.test_pickle         always succeeds (executed directly)
  -m test test_pickle         always fails (executed via test module)
  -m test -w -j1 test_pickle  fails, but succeeds on retry

The failures seem to always occur in CPicklerTests.test_bad_getattr.  I'm not sure how to run that single test via the test module, but limiting to all CPicklerTests tests or all test_bad_getattr tests succeeds even through the test module.

The last scenario above (successful retry) has to use -j or else no retry (-w) takes place.  That's the path the buildbots are following.
Date User Action Args
2021-11-14 18:56:00db3lsetrecipients: + db3l, gregory.p.smith, Carl.Friedrich.Bolz, r.david.murray, lukasz.langa, serhiy.storchaka, Bruno Oliveira, Daniel Lepage, Jim Fasarakis-Hilliard, louielu, pablogsal, miss-islington, Dennis Sweeney, iritkatriel
2021-11-14 18:56:00db3lsetmessageid: <>
2021-11-14 18:56:00db3llinkissue30570 messages
2021-11-14 18:56:00db3lcreate