-
Notifications
You must be signed in to change notification settings - Fork 213
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
Race condition in pytest-dev hangs coverage 6.3 #520
Comments
pytest-cov basically just forcibly enables coverage in multiprocess's subprocesses but that in turn just spurs problems caused by locks being shared between processes after a fork. |
I think I have seen race conditions between erasing the data files and writing new data. I'm working on getting more information. |
pytest-cov does have a different way of setting up for multiprocessing (using register_after_fork and a finalizer) - maybe I could try to just copy whatever coverage has for subprocesses (reusing won't work since there's a different way coverage configuration is being set) but still, using fork mode is just asking for trouble... |
See nedbat/coveragepy#1310 . Removing pytest-cov solves the problem. What is pytest-cov doing that causes this problem?
The text was updated successfully, but these errors were encountered: