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 with Python3.8b2 breaks multiprocessing #828
Labels
bug
Something isn't working
Comments
an even tinier repro (might make a nice test case ;) ):
|
Thanks, this is fixed in version 4.5.4, and 5.0a5. |
@nedbat Thank you for the quick fix. This has been causing us trouble for a while. |
This was referenced Jun 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using coverage with
concurrency=multiprocessing
under Python3.8b2, forked processes don't fully init. The child worker process starts, and the process init code runs, but the actual Processrun
target never executes. The minimal repro sample below works fine under other released versions of Python.To Reproduce
How can we reproduce the problem? Please be specific.
repro.py
coverage3 run --concurrency=multiprocessing repro.py
Expected behavior
child workloads complete, "done" is printed (along with some debug info)
Additional context
We started hitting this recently in Ansible's nightly coverage runs (which include Python 3.8 prereleases as a canary)...
The text was updated successfully, but these errors were encountered: