Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_sys triggers a fatal python error when run under coverage.py #55194

Closed
brettcannon opened this issue Jan 23, 2011 · 6 comments
Closed

test_sys triggers a fatal python error when run under coverage.py #55194

brettcannon opened this issue Jan 23, 2011 · 6 comments
Labels
release-blocker type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@brettcannon
Copy link
Member

BPO 10985
Nosy @brettcannon, @birkenfeld
Files
  • issue10985.diff: Make test_sys.test_recursionlimit_recovery CPython-only & sys.gettrace() is false
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2011-01-23.23:06:35.348>
    created_at = <Date 2011-01-23.00:18:05.991>
    labels = ['type-crash', 'release-blocker']
    title = 'test_sys triggers a fatal python error when run under coverage.py'
    updated_at = <Date 2011-01-23.23:06:35.347>
    user = 'https://github.com/brettcannon'

    bugs.python.org fields:

    activity = <Date 2011-01-23.23:06:35.347>
    actor = 'brett.cannon'
    assignee = 'none'
    closed = True
    closed_date = <Date 2011-01-23.23:06:35.348>
    closer = 'brett.cannon'
    components = []
    creation = <Date 2011-01-23.00:18:05.991>
    creator = 'brett.cannon'
    dependencies = []
    files = ['20496']
    hgrepos = []
    issue_num = 10985
    keywords = ['patch']
    message_count = 6.0
    messages = ['126865', '126866', '126867', '126900', '126905', '126907']
    nosy_count = 2.0
    nosy_names = ['brett.cannon', 'georg.brandl']
    pr_nums = []
    priority = 'release blocker'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'crash'
    url = 'https://bugs.python.org/issue10985'
    versions = ['Python 3.2']

    @brettcannon
    Copy link
    Member Author

    If you run test_sys under coverage.py with ./python.exe -m coverage run --pylib [Lib/test/regrtest.py](https://github.com/python/cpython/blob/main/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 the recursion, but coverage.py is being used w/o its extension coverage support. Could be caused by coverage.py, but I'm a bit surprised that it's a fatal error instead of a recursion limit exception.

    @brettcannon brettcannon added the type-crash A hard crash of the interpreter, possibly with a core dump label Jan 23, 2011
    @brettcannon
    Copy link
    Member Author

    Ran the test under verbose mode at Antoine's suggestion; test triggering the failure is test_recursionlimit_recovery

    @brettcannon
    Copy link
    Member Author

    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.

    @brettcannon
    Copy link
    Member Author

    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.

    @brettcannon
    Copy link
    Member Author

    Georg cleared the commit; just waiting for a test run with coverage.py to finish before committing.

    @brettcannon
    Copy link
    Member Author

    r88153 w/ a review by Georg Brandl

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    release-blocker type-crash A hard crash of the interpreter, possibly with a core dump
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant