-
-
Notifications
You must be signed in to change notification settings - Fork 439
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
Coverage command_line run fails with AttributeError: 'NoDebugging' object has no attribute 'suppress_callers' #1904
Comments
|
I'm looking in using an alternative. I'm working on cleaning this up at the moment. But don't you think what I mentioned in the original post is not weird as well ? With the usage of an undefined variable. |
I see your point. I fixed NoDebugging. Can you try installing this and see if it fixes the problem?
|
Thanks ! I will try (may take some time since I was checking this in parallel of something else) and let you know ! |
This is now fixed in commit 9793270. |
Describe the bug
Coverage command_line run fails with AttributeError: 'NoDebugging' object has no attribute 'suppress_callers'
To Reproduce
How can we reproduce the problem? It's hard to reproduce, this is a sporadic issue that we are seeing running some automated tests in endurance.
pip freeze
is helpful.Full stack trace:
Seems like issue is here:
coveragepy/coverage/debug.py
Lines 81 to 89 in 8c2ea9a
Which should be defined here:
coveragepy/coverage/debug.py
Line 54 in 8c2ea9a
But in our case it isn't because it seems the underlying code uses the NoDebugging class which doesn't call the init of its parent:
coveragepy/coverage/debug.py
Lines 111 to 118 in 8c2ea9a
Hard to give full repro steps since this is seen on some of unit test, but we basically run our software with the following coverage script which wraps the python code we want to test/check the coverage for. It's mostly a wrapper so that we can trigger the dump of the coverage periodically or on demand through a redis message
the issue only occurs sporadically, reproduction is not 100%.
Expected behavior
Running a software with the CoverageScript.command_line should have deterministic behavior and not fail sporadically.
The text was updated successfully, but these errors were encountered: