-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Investigate win failures #6351
Investigate win failures #6351
Conversation
It generates huge amounts of output which makes it harder to follow what's happening. This is useful mainly when the tests are crashing for unknown reasons, in which case then it makes sense to add it back for debugging.
Strange, the failure is happening due to some atexit-registered function raising an exception:
I've commented the only place where pytest registers a function, but the error still happens. I suspect this is caused because the project is cloned and executed from |
the python 2 failure seems to be much more helpful:
|
here's the issue in coveragepy: nedbat/coveragepy#895 |
No description provided.