[issue10985] test_sys triggers a fatal python error when run under coverage.py

Brett Cannon added the comment: r88153 w/ a review by Georg Brandl -- resolution: accepted -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker

[issue10985] test_sys triggers a fatal python error when run under coverage.py

Brett Cannon added the comment: Georg cleared the commit; just waiting for a test run with coverage.py to finish before committing. -- resolution: -> accepted stage: unit test needed -> commit review ___ Python tracker

[issue10985] test_sys triggers a fatal python error when run under coverage.py

Brett Cannon added the comment: I have a patch for this which makes it a CPython-only test along with being conditional if a trace function is set. Making it a release blocker to see if Georg will let me commit it. -- keywords: +patch nosy: +georg.brandl priority: normal -> release bl

[issue10985] test_sys triggers a fatal python error when run under coverage.py

Brett Cannon added the comment: The comment on the test says its brittle and sensitive to nothing mucking around with recursion depth, so the test probably need a unittest.skipIf check for a trace function. -- ___ Python tracker

[issue10985] test_sys triggers a fatal python error when run under coverage.py

Brett Cannon added the comment: Ran the test under verbose mode at Antoine's suggestion; test triggering the failure is test_recursionlimit_recovery -- ___ Python tracker ___ _

[issue10985] test_sys triggers a fatal python error when run under coverage.py

New submission from Brett Cannon : If you run test_sys under coverage.py with ``./python.exe -m coverage run --pylib Lib/test/regrtest.py test_sys`` you get:: Fatal Python error: Cannot recover from stack overflow Have not taken the time to try to figure out exactly what code is triggering