-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
test_multiprocessing_fork: test_nested_startmethod() fails randomly. #109706
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
tests
Tests in the Lib/test dir
Comments
vstinner
added a commit
to vstinner/cpython
that referenced
this issue
Sep 22, 2023
Don't check order, queue items can be written in any order.
vstinner
added a commit
to vstinner/cpython
that referenced
this issue
Sep 22, 2023
Don't check order, queue items can be written in any order.
vstinner
added a commit
that referenced
this issue
Sep 22, 2023
Don't check order, queue items can be written in any order.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Sep 22, 2023
…nGH-109707) Don't check order, queue items can be written in any order. (cherry picked from commit b03a791) Co-authored-by: Victor Stinner <vstinner@python.org>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Sep 22, 2023
…nGH-109707) Don't check order, queue items can be written in any order. (cherry picked from commit b03a791) Co-authored-by: Victor Stinner <vstinner@python.org>
csm10495
pushed a commit
to csm10495/cpython
that referenced
this issue
Sep 28, 2023
…n#109707) Don't check order, queue items can be written in any order.
Glyphack
pushed a commit
to Glyphack/cpython
that referenced
this issue
Sep 2, 2024
…n#109707) Don't check order, queue items can be written in any order.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
test_nested_startmethod() fails randomly. Since there is no synchronization, putting items in the queue is not really ordered.
I suggest to either accept [1, 2] and [2, 1] in the test, or add some kind of synchronization to ensure that events happen in the expected order. Here I don't think that order matters.
The test was added by PR #108568 of issue gh-108520.
build: https://buildbot.python.org/all/#/builders/503/builds/3941
The failure can be reproduced by stressing the test:
Linked PRs
The text was updated successfully, but these errors were encountered: