-
-
Notifications
You must be signed in to change notification settings - Fork 426
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
multiprocessing.Manager() + cd leads to EOFError #890
Comments
Avoid bug in coverage 5.0 nedbat/coveragepy#890
Avoid bug in coverage 5.0 nedbat/coveragepy#890
Avoid bug in coverage 5.0 nedbat/coveragepy#890
Avoid bug in coverage 5.0 nedbat/coveragepy#890
Hmm, something is different for me here on Mac OS. Under Python 3.8, I see the same behavior either with or without coverage, and with coverage==4.5.4 or coverage==5.0.1. I get a stack trace like this:
If I change the code to this, it works under either:
I'm not sure what the code is meant to do, and so which should go in the |
Thanks for spending time on it! I'm sorry to not emphasize [run]
concurrency = multiprocessing Without concurrency setting it doesn't throw. The bug is 100% reproducible on all OS and python versions I've tried. I've set up a small repo to demonstrate, please see it's travis build failures. For some reason windows builds hang forever after first failure command, therefore I cancelled windows jobs after first failure. (I'm not good at windows scripting, please tell how to fix if you know) Note there are two scripts: |
Here is build of https://travis-ci.com/sizmailov/reproduce-coverage-bug-890/builds/142106771 No failures. |
Thanks, the repo helps with the details. |
This is now fixed in df82a96. Thanks for the detailed report. |
This is now available in coverage 5.0.2 |
Describe the bug
Change of directory + multiprocessing.Manager() entrance results to EOFError with coverage 5.0
To Reproduce
What version of Python are you using?
Python 3.8.0rc1
It also fails on travis with
Python 3.6.3
What version of coverage.py are you using?
coverage debug sys
python -m coverage run repro.py
python repro.py
Expected behavior
ok
messageAdditional context
Seems like bug was introduced with 5.0 release
The text was updated successfully, but these errors were encountered: