bpo-45209: fix UserWarning: resource_tracker in test_multiprocessing#28377
bpo-45209: fix UserWarning: resource_tracker in test_multiprocessing#28377ambv merged 4 commits into
UserWarning: resource_tracker in test_multiprocessing#28377Conversation
UserWarning: resource_tracker in `test_multiproc…|
All PRs right now have this problem: https://dev.azure.com/Python/cpython/_build/results?buildId=87889&view=logs&j=91c152bd-7320-5194-b252-1404e56e2478&t=c7e99cd8-4756-5292-d34b-246ff5fc615f Another examples: |
Sorry, something went wrong.
|
Windows build error on Azure Pipelines is tracked by: https://bugs.python.org/issue45220 |
Sorry, something went wrong.
8ebb6f6 to
95b5858
Compare
September 16, 2021 19:52
|
Rebased, CI now passes. |
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
LGTM. @pitrou: Would you mind to double check this multiprocessing test fix?
I'm kind of unhappy that you have to prepend "/". SharedMemory._prepend_leading_slash does a magic dance (add/remove "/" prefix) with SharedMemory(name) constructor parameter and in SharedMemory.name property. But I don't think that it's worth it to add something just for this very specific test. We can always revisit the code later if we start to have issue on some corner cases.
Sorry, something went wrong.
Yes, me too. I've tried several other things like |
Sorry, something went wrong.
|
Since the slash hack is tests-only, let's have it. We can fix the fix later if we find a way to do so. |
Sorry, something went wrong.
pythonGH-28377) (cherry picked from commit f604cf1) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
pythonGH-28377) (cherry picked from commit f604cf1) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
https://bugs.python.org/issue45209