Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[3.9] [3.10] gh-91607: Fix several test_concurrent_futures tests to actually test what they claim (GH-91600) (GH-91612)#91617

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
gpshead merged 2 commits intopython:3.9fromgpshead:backport-9a45893-3.9
Apr 17, 2022

Conversation

@gpshead
Copy link
Member

  • 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 commit7fa3a5a)
(cherry picked from commit9a45893)

…s to actually test what they claim (pythonGH-91600) (pythonGH-91612)* Fix test_concurrent_futures to actually test what it says.Many ProcessPoolExecutor based tests were ignoring the mp_contextand using the default instead.  This meant we lacked proper testcoverage of all of them.Also removes the old _prime_executor() worker delay seeding codeas it appears to have no point and causes 20-30 seconds extralatency on this already long test.  It also interfered with someof the refactoring to fix the above to not needlessly create theirown executor when setUp has already created an appropriate one.* Don't import the name from multiprocessing directly to avoid confusion.(cherry picked from commit7fa3a5a)Co-authored-by: Gregory P. Smith <greg@krypto.org>.(cherry picked from commit9a45893)Co-authored-by: Gregory P. Smith <greg@krypto.org>
@gpsheadgpshead added type-bugAn unexpected behavior, bug, or error testsTests in the Lib/test dir labelsApr 16, 2022
@gpsheadgpshead self-assigned thisApr 16, 2022
@gpsheadgpshead merged commit2a43afd intopython:3.9Apr 17, 2022
@gpsheadgpshead deleted the backport-9a45893-3.9 branchApril 18, 2022 22:16
hello-adam pushed a commit to hello-adam/cpython that referenced this pull requestJun 2, 2022
…s to actually test what they claim (pythonGH-91600) (pythonGH-91612) (python#91617)* Fix test_concurrent_futures to actually test what it says.Many ProcessPoolExecutor based tests were ignoring the mp_contextand using the default instead.  This meant we lacked proper testcoverage of all of them.Also removes the old _prime_executor() worker delay seeding codeas it appears to have no point and causes 20-30 seconds extralatency on this already long test.  It also interfered with someof the refactoring to fix the above to not needlessly create theirown executor when setUp has already created an appropriate one.* Don't import the name from multiprocessing directly to avoid confusion.(cherry picked from commit7fa3a5a)(cherry picked from commit9a45893)
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

@gpsheadgpshead

Labels

testsTests in the Lib/test dirtype-bugAn unexpected behavior, bug, or error

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

test_concurrent_futures does not exercise each mp_context method reliably due to code smell

2 participants

@gpshead@bedevere-bot

[8]ページ先頭

©2009-2025 Movatter.jp