[issue41970] test_lib2to3 fails since Python 3.9

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue41970] test_lib2to3 fails since Python 3.9

Pablo Galindo Salgado added the comment: New changeset c6f41e62f55933f9735e9b9c103c6860685b028a by Karthikeyan Singaravelan in branch '3.9': [3.9] bpo-41970: Avoid test failure in test_lib2to3 if the module is already imported (GH-22595) (GH-22609)

[issue41970] test_lib2to3 fails since Python 3.9

Change by Karthikeyan Singaravelan : -- pull_requests: +21592 pull_request: https://github.com/python/cpython/pull/22609 ___ Python tracker ___

[issue41970] test_lib2to3 fails since Python 3.9

miss-islington added the comment: New changeset 4a9f82f50d957b6cf3fd207de8b583d9137316b8 by Pablo Galindo in branch 'master': bpo-41970: Avoid test failure in test_lib2to3 if the module is already imported (GH-22595)

[issue41970] test_lib2to3 fails since Python 3.9

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +21583 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22595 ___ Python tracker

[issue41970] test_lib2to3 fails since Python 3.9

Karthikeyan Singaravelan added the comment: I guess this could be due to loading the module twice where the warning is not emitted again on reimport which test__all__ seems to do so by importing lib2to3. One obvious fix would be to pass quiet=True. Else we need to find a way to import the

[issue41970] test_lib2to3 fails since Python 3.9

Pablo Galindo Salgado added the comment: Ok, thanks everyone for the help reproducing this. I think I can work on a fix today -- ___ Python tracker ___

[issue41970] test_lib2to3 fails since Python 3.9

Federico Granata added the comment: I can have the test to fails if I run "python -m test test_lib2to3 test_lib2to3" as well -- ___ Python tracker ___

[issue41970] test_lib2to3 fails since Python 3.9

Karthikeyan Singaravelan added the comment: I can reproduce this by running test_lib2to3 twice or running test___all__ with test_lib2to3 ./python -m test test_lib2to3 test_lib2to3 0:00:00 load avg: 0.03 Run tests sequentially 0:00:00 load avg: 0.03 [1/2] test_lib2to3 0:00:13 load avg: 0.25

[issue41970] test_lib2to3 fails since Python 3.9

Federico Granata added the comment: I just run "python -m test" for it to fail and "python -m test test_lib2to3" for it to succeded. -- ___ Python tracker ___

[issue41970] test_lib2to3 fails since Python 3.9

Felix Yan added the comment: I use this in Arch's packaging: LC_CTYPE=en_US.UTF-8 xvfb-run -s "-screen 0 1920x1080x16 -ac +extension GLX" -a -n "$servernum" \ "${srcdir}/Python-${pkgver}/python" -m test.regrtest -v -uall -x test_tk (test_tk is currently skipped due to

[issue41970] test_lib2to3 fails since Python 3.9

Karthikeyan Singaravelan added the comment: Pablo, I can see the error in Travis. The difference I can see is that the tests are executed sequentially in coverage run but normal run has tests executing in parallel. Felix and Federico, can you please add the command you use to run the tests?

[issue41970] test_lib2to3 fails since Python 3.9

Federico Granata added the comment: I just experienced the very same issue. I use pyenv and doing all tests gives me a failure on test_lib2to3 while running it individually end succesfully. Tell me if I can provide any useful information -- nosy: +federico.granata

[issue41970] test_lib2to3 fails since Python 3.9

Pablo Galindo Salgado added the comment: > I have also seen this and linked issue on running whole test suite while > building python myself but running individual tests show no error and > buildbots also never complained so I thought it's something wrong with my > setup. I introduced the

[issue41970] test_lib2to3 fails since Python 3.9

Karthikeyan Singaravelan added the comment: I have also seen this and linked issue on running whole test suite while building python myself but running individual tests show no error and buildbots also never complained so I thought it's something wrong with my setup. I introduced the commit

[issue41970] test_lib2to3 fails since Python 3.9

Pablo Galindo Salgado added the comment: Same thing as in https://bugs.python.org/issue41971. I cannot reproduce this with a fresh install of 3.9 and our buildbots are not complaining about this. ownloads/Python-3.9.0 ❯ ./python -m test test_lib2to3 0:00:00 load avg: 3.64 Run tests

[issue41970] test_lib2to3 fails since Python 3.9

New submission from Felix Yan : I am packaging Python for Arch and the tests suite of Python 3.8.6 pass here without this: ``` 0:09:06 load avg: 0.87 [205/424] test_lib2to3