]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.14] gh-83386: Enable test_hang_gh83386 for ProcessPoolExecutor (GH-152976) (#152983)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Sat, 4 Jul 2026 03:35:35 +0000 (05:35 +0200)
committerGitHub <noreply@github.com>
Sat, 4 Jul 2026 03:35:35 +0000 (03:35 +0000)
commit058a5c61be5411e53f488ddc0423c85c8bca6138
tree0912eb0ad2527caf66f224b883ef212e90228963
parent8a8c8ee3f9c6ef1c95502338bd50b15513d530ac
[3.14] gh-83386: Enable test_hang_gh83386 for ProcessPoolExecutor (GH-152976) (#152983)

gh-83386: Enable test_hang_gh83386 for ProcessPoolExecutor (GH-152976)

The hang this test guards against (interpreter exit after
shutdown(wait=False) with running futures) was fixed for
ProcessPoolExecutor by the executor management rewrite years ago, but
the test still skipped it citing the issue. The skip also hid a latent
NameError in the subprocess template, which only selects a start method
in the process pool variants; rewrite it to use the same
mp_context=get_context() shape as the sibling templates. Remove a stale
comment claiming ProcessPoolExecutor often hangs with wait=False.
(cherry picked from commit 548c7314138b85cab3b945a1ce05440dd836a2ea)

Co-authored-by: Gregory P. Smith <68491+gpshead@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Lib/test/test_concurrent_futures/test_shutdown.py