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.21:16:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1619558166.24.0.619381368195.issue43955@roundup.psfhosted.org>
In-reply-to
Content
Shreyan Avigyan:
> And the "(Pdb) continue (...) actually is manually entered by me.

Victor Stinner:
Do you mean that you modified the Python source code?

Me:
Doubt it. For me, with more words: the "(Pdb) " prompt appears all by itself, by magic, and the test run is stuck then. I bet Shreyan meant to say "so I manually entered 'continue [RETURN]' at the pdb prompt to get it unstuck again".

> Does the issue go away if you revert your change or
> if you test a newly installed Python?

For me, I was using Win10 x64 CPython built from yesterday's github master/main.

And thanks for the distutils clue! I bet that one is a distinct issue.

To make it more confusing, all 4 tests passed when I ran with `-j` (to force parallel test execution) - but then test_compileall failed instead :-)
History
Date User Action Args
2021-04-27 21:16:06tim.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 21:16:06tim.peterssetmessageid: <1619558166.24.0.619381368195.issue43955@roundup.psfhosted.org>
2021-04-27 21:16:06tim.peterslinkissue43955 messages
2021-04-27 21:16:06tim.peterscreate