-
-
Notifications
You must be signed in to change notification settings - Fork 343
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
non-deterministic deadlock in test_subprocess::test_warn_on_failed_cancel_terminate #1604
Comments
Ick. the |
It can lead to confusion, e.g.: python-trio#1604
OK, yeah, the problem doesn't seem to be
So that thread is just a stray one left behind by that test. Probably not relevant to this hang. It's weird for pytest to hang without printing which test it's starting... I guess the next test it would have run is |
It's too bad the faulthandler output is useless here. This is one of those times when #927 would be really helpful |
https://travis-ci.org/github/python-trio/trio/jobs/697497032 confirms this happens in test_warn_on_failed_cancel_terminate as Travis is much better at showing output while the tests are still running. The not so relevant stacktrace:
|
And again on FreeBSD: https://travis-ci.org/github/python-trio/trio/jobs/697564639 |
I managed to get a pytest traceback by using pytest-timeout and pytest-flakefinder, not sure if it helps or not. https://github.com/pquentin/trio/runs/765304561 (Notice that the test gets interrupted by pytest-timeout after one second.)
|
See https://github.com/python-trio/trio/runs/756580934?check_suite_focus=true. I was able to retrieve the test name thanks to the traceback. The test timed out on an acquire() call.
The text was updated successfully, but these errors were encountered: