[issue39983] test.regrtest: test marked as failed (env changed), but no warning: test_multiprocessing_forkserver
STINNER Victor
report at bugs.python.org
Thu Apr 23 20:56:33 EDT 2020
STINNER Victor <vstinner at python.org> 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 (env changed) (3 min 39 sec) -- running: test_peg_generator (2 min 3 sec)
Warning -- Unraisable exception
test_cancel (test.test_concurrent_futures.FutureTests) ... ok
test_cancelled (test.test_concurrent_futures.FutureTests) ... ok
(...)
test_first_exception_some_already_complete (test.test_concurrent_futures.ThreadPoolWaitTests) ... ok
test_pending_calls_race (test.test_concurrent_futures.ThreadPoolWaitTests) ... ok
test_timeout (test.test_concurrent_futures.ThreadPoolWaitTests) ... ok
----------------------------------------------------------------------
Ran 193 tests in 219.248s
OK (skipped=6)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue39983>
_______________________________________
More information about the Python-bugs-list
mailing list