]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.9] [3.10] gh-91607: Fix several test_concurrent_futures tests to actually test...
authorGregory P. Smith <greg@krypto.org>
Sun, 17 Apr 2022 05:47:41 +0000 (22:47 -0700)
committerGitHub <noreply@github.com>
Sun, 17 Apr 2022 05:47:41 +0000 (22:47 -0700)
commit2a43afdba94b86e1e11e8d311c66e40b77675500
tree82a8d2ca3626904e32312763354fe1956d59f0c2
parentc171d757f3892263e163eddd702ae5249308404d
[3.9] [3.10] gh-91607: Fix several test_concurrent_futures tests to actually test what they claim (GH-91600) (GH-91612) (#91617)

* Fix test_concurrent_futures to actually test what it says.

Many ProcessPoolExecutor based tests were ignoring the mp_context
and using the default instead.  This meant we lacked proper test
coverage of all of them.

Also removes the old _prime_executor() worker delay seeding code
as it appears to have no point and causes 20-30 seconds extra
latency on this already long test.  It also interfered with some
of the refactoring to fix the above to not needlessly create their
own executor when setUp has already created an appropriate one.

* Don't import the name from multiprocessing directly to avoid confusion.

(cherry picked from commit 7fa3a5a2197896066e3fe53ee325ac6ab54c3414)
(cherry picked from commit 9a458934f7be37c59525350f1f9ecbdcd69903c1)
Lib/test/test_concurrent_futures.py
Misc/NEWS.d/next/Tests/2022-04-16-17-54-05.gh-issue-91607.FnXjtW.rst [new file with mode: 0644]