[issue46465] test_unittest: TestBreakSignalDefault.testInstallHandler() fails if run after TestBreak

Guido van Rossum added the comment: @kj, are you looking into this? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue46465] test_unittest: TestBreakSignalDefault.testInstallHandler() fails if run after TestBreak

STINNER Victor added the comment: Attached bug.py reproduces the bug without unittest, just run: ./python bug.py On Python 3.10, it writes: --- LOOP 0 LOOP 1 (...) LOOP 14 LOOP 15 --- On the main branch, it fails with: --- LOOP 0 LOOP 1 LOOP 2 LOOP 3 LOOP 4 LOOP 5 LOOP 6 LOOP 7 Traceback (mo

[issue46465] test_unittest: TestBreakSignalDefault.testInstallHandler() fails if run after TestBreak

STINNER Victor added the comment: It's a regression introduced by the following change: commit 3163e68c342434db37c69669017f96a4bb2d5f13 Author: Ken Jin <28750310+fidget-spin...@users.noreply.github.com> Date: Wed Oct 20 07:16:36 2021 +0800 bpo-44525: Specialize ``CALL_FUNCTION`` for C f

[issue46465] test_unittest: TestBreakSignalDefault.testInstallHandler() fails if run after TestBreak

New submission from STINNER Victor : test_unittest: TestBreakSignalDefault.testInstallHandler() fails if run after TestBreak: - $ ./python -m test -v test_unittest -R 3:3 -m '*TestBreak.testHandlerReplacedButCalled' -m '*TestBreak.testInstallHandler' -m '*TestBreakSignalDefault.testIn