[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

STINNER Victor added the comment: "Warning -- Unraisable exception" is now logged, but the exceptions is not when sys.stderr is redirected. That's better than nothing, so I close the issue. Moreover, test_multiprocessing_forkserver has been fixed. -- resolution: -> fixed stage:

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

STINNER Victor added the comment: test_concurrent_futures "unraisable exception" may be bpo-39995. -- ___ Python tracker ___ ___

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

STINNER Victor added the comment: Oh nice, my fix worked as expected: "Warning -- Unraisable exception" was logged! But the unraisable exception itself was not logged. https://buildbot.python.org/all/#/builders/612/builds/292 0:04:02 load avg: 8.11 [421/423/1] test_concurrent_futures failed

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

STINNER Victor added the comment: New changeset 3340b2a61b458e7087c8c5fea063b1b45e1a4a07 by Victor Stinner in branch '3.8': bpo-39983: Add test.support.print_warning() (GH-19683) (GH-19687) https://github.com/python/cpython/commit/3340b2a61b458e7087c8c5fea063b1b45e1a4a07 --

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

Change by STINNER Victor : -- pull_requests: +19006 pull_request: https://github.com/python/cpython/pull/19687 ___ Python tracker ___

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

STINNER Victor added the comment: New changeset d663d34685e18588748569468c672763f4c73b3e by Victor Stinner in branch 'master': bpo-39983: Add test.support.print_warning() (GH-19683) https://github.com/python/cpython/commit/d663d34685e18588748569468c672763f4c73b3e --

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

Change by STINNER Victor : -- keywords: +patch pull_requests: +19003 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19683 ___ Python tracker ___

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

STINNER Victor added the comment: Another example: test_asyncio on AMD64 Fedora Stable Clang 3.x https://buildbot.python.org/all/#/builders/226/builds/630 -- ___ Python tracker

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

STINNER Victor added the comment: Another example with test_asyncio on s390x RHEL7 3.x: https://buildbot.python.org/all/#/builders/320/builds/410 -- ___ Python tracker ___

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

STINNER Victor added the comment: Another example: AMD64 RHEL7 LTO 3.7 "1 test altered the execution environment: test_multiprocessing_spawn" https://buildbot.python.org/all/#/builders/43/builds/138 -- ___ Python tracker

[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver

New submission from STINNER Victor : Tests run with --fail-env-changed. test_multiprocessing_forkserver failed with "env changed", but no warning was logged to explain why :-( PPC64LE RHEL7 3.8: https://buildbot.python.org/all/#/builders/401/builds/69 ./python ./Tools/scripts/run_tests.py