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 tim.peters
Recipients Guido.van.Rossum, Mark.Shannon, corona10, gvanrossum, paul.moore, serhiy.storchaka, shihai1991, shreyanavigyan, steve.dower, tim.golden, tim.peters, vstinner, zach.ware
Date 2021-04-27.18:46:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I expect parallelism is a red herring: early in the test output attached to this report:

0:00:04 Run tests sequentially

and there's no other evidence in the output that multiple tests are running simultaneously.

Also on Win10, the 4 failing tests here pass for me if I run them one at a time, so it's not obvious.

I _suspect_ that what's going wrong with test_pdb is the root cause: every now & again, for some weeks now, when I try to run tests on Windows I come back to the cmd.exe window and see that it's just sitting there, waiting at a pdb prompt.

In the output attached to this report, note that after test_threading starts, 

(Pdb) continue
(Pdb) continue
(Pdb) continue
(Pdb) continue

appears out of the blue. But test_pdb is long finished by that time.

But I'm clueless about current pdb internals.
Date User Action Args
2021-04-27 18:47:00tim.peterssetrecipients: + tim.peters, gvanrossum, paul.moore, vstinner, tim.golden, Mark.Shannon, zach.ware, serhiy.storchaka, steve.dower, Guido.van.Rossum, corona10, shihai1991, shreyanavigyan
2021-04-27 18:47:00tim.peterssetmessageid: <>
2021-04-27 18:47:00tim.peterslinkissue43955 messages
2021-04-27 18:46:59tim.peterscreate