| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
… mid-result A worker killed after writing part of a large result left the manager thread blocked in Connection.recv(). The parent holds the result pipe's write end, so that death is not delivered as EOF. Watch worker sentinels for the rest of the message and raise BrokenProcessPool.
Sorry, something went wrong.
|
The remaining Windows (free-threading) x64 tail-call failure is in test_urllib2net (test_ftp_no_leak and test_ftp_timeout): ftp://www.pythontest.net returned "425 Security: Bad IP connecting." test_process_pool passed. This looks like the known runner flake from #79592. Could a triager re-run the failed job? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Fixes #159689.
A ProcessPoolExecutor worker killed while writing a large result left the future pending and blocked interpreter shutdown. Connection.recv() now watches worker sentinels for the rest of the message and raises BrokenProcessPool. Callers that do not pass sentinels keep the previous behavior.
Test plan