[issue43843] libregrtest: mark a test as failed if a thread logs an unexpected exception

Change by STINNER Victor : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue43843] libregrtest: mark a test as failed if a thread logs an unexpected exception

STINNER Victor added the comment: test_concurrent_futures logs two warnings: I created bpo-43867 for this one. -- ___ Python tracker ___ __

[issue43843] libregrtest: mark a test as failed if a thread logs an unexpected exception

STINNER Victor added the comment: test_concurrent_futures logs two warnings. s390x Debian 3.x: https://buildbot.python.org/all/#/builders/49/builds/1124 AMD64 RHEL7 3.x: https://buildbot.python.org/all/#/builders/15/builds/1074 0:03:18 load avg: 4.78 [302/427] test_concurrent_futures passed

[issue43843] libregrtest: mark a test as failed if a thread logs an unexpected exception

STINNER Victor added the comment: New changeset b136b1aac4b7d07e3120ee59e41c02bc86032162 by Victor Stinner in branch 'master': bpo-43843: libregrtest uses threading.excepthook (GH-25400) https://github.com/python/cpython/commit/b136b1aac4b7d07e3120ee59e41c02bc86032162 -- __

[issue43843] libregrtest: mark a test as failed if a thread logs an unexpected exception

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

[issue43843] libregrtest: mark a test as failed if a thread logs an unexpected exception

New submission from STINNER Victor : The Python test runner (libregrtest) should mark a test as failed if a thread logs an unexpected exception, as already done with unraisable exception. See for example bpo-43842 where test_logging logs the following exception, but the tes is marked as passe