]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.15] gh-83386: Enable test_hang_gh83386 for ProcessPoolExecutor (GH-152976) (#152982)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Fri, 3 Jul 2026 21:32:20 +0000 (23:32 +0200)
committerGitHub <noreply@github.com>
Fri, 3 Jul 2026 21:32:20 +0000 (21:32 +0000)
commit8d08232817dfb14e86f26087f6f090da6f48884a
tree82e109bf872498050878d5739dfc8ca90087f33a
parentce373b845ce822a413ee8eb9bf161270825b38a2
[3.15] gh-83386: Enable test_hang_gh83386 for ProcessPoolExecutor (GH-152976) (#152982)

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