[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread STINNER Victor
STINNER Victor added the comment: Thanks everyone for fixing these issues and thanks Shreyan for the bug report. The main initial is now fixed, so I close the issue. Let's continue the discussions in remaining open issues: * bpo-37387: test_compileall fails randomly on Windows when tests

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread Steve Dower
Steve Dower added the comment: New changeset c1a9535989cc7323099725503519a17f79d083f5 by Steve Dower in branch 'master': bpo-43955: Handle the case where the distutils warning has already been triggered (GH-25675)

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread STINNER Victor
STINNER Victor added the comment: > Another issue with the tests is that it has become terribly slow. It's taking > about 45 minutes to complete 1 run of the test suite. A few days ago, it took > only 10 - 15 minutes. It took 49 minutes on my Windows 10 VM. Are you sure that you ran the

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread STINNER Victor
STINNER Victor added the comment: I ran "python -m test" on an up to date master branch (commit fe52eb62191e640e720d184a9a1a04e965b8a062), there is a single remaining issue. test_distutils failed because the deprecation warning was already emited: issue fixed by PR 25675. The other issues

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread Shreyan Avigyan
Shreyan Avigyan added the comment: All the test failures are side effects of other tests because when they are ran individually they do not trigger errors. Running sequentially causes the error. -- ___ Python tracker

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread Shreyan Avigyan
Shreyan Avigyan added the comment: I ran the test again and test_signal still modifies sys.gettrace() -- ___ Python tracker ___

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread Shreyan Avigyan
Shreyan Avigyan added the comment: FYI test_signal is no longer modifying sys.gettrace thanks to your fix. But test_threading still does. Do you have a fix for that? -- ___ Python tracker

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread Shreyan Avigyan
Shreyan Avigyan added the comment: Same errors. (Recompilation was done 1 or 2 hours ago against the then updated master branch. It may not include the latest commit) -- ___ Python tracker

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread STINNER Victor
STINNER Victor added the comment: Shreyan Avigyan: please try an up to date version of the master branch, I fixed the Pdb issue with commit a09766deab5aff549f40f27080895e148af922ed. -- ___ Python tracker

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-28 Thread Shreyan Avigyan
Shreyan Avigyan added the comment: Another issue with the tests is that it has become terribly slow. It's taking about 45 minutes to complete 1 run of the test suite. A few days ago, it took only 10 - 15 minutes. And moreover I think test_threading is also modifying sys.gettrace. The logs

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-27 Thread Steve Dower
Change by Steve Dower : -- keywords: +patch pull_requests: +24366 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25675 ___ Python tracker ___

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-27 Thread STINNER Victor
STINNER Victor added the comment: FYI I used the following patch to debug this issue: diff --git a/Lib/unittest/case.py b/Lib/unittest/case.py index 872f121127..ee2e1ff77f 100644 --- a/Lib/unittest/case.py +++ b/Lib/unittest/case.py @@ -546,6 +546,8 @@ def _callSetUp(self):

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-27 Thread STINNER Victor
STINNER Victor added the comment: Running these 3 tests is enough to reproduce the issue: --- vstinner@DESKTOP-DK7VBIL C:\vstinner\python\master>python -m test test_interpreters test_pdb test_threading Running Debug|x64 interpreter... 0:00:00 Run tests sequentially 0:00:00

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-27 Thread STINNER Victor
STINNER Victor added the comment: See also bpo-43963: "test_interpreters has side effects on test_signal". -- ___ Python tracker ___

[issue43955] Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt

2021-04-27 Thread STINNER Victor
Change by STINNER Victor : -- title: Test Failures on Windows 10 -> Windows: Running the Python test suite sequentially is interrupted by (Pdb) prompt ___ Python tracker ___