-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
gh-109401: Fix threading barrier test_default_timeout() #109875
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
Conversation
Increase timeouts. Barrier default timeout should be long enough to spawn 4 threads on a slow CI.
a24531d
to
ca0d11e
Compare
This test is not reliable, it depends on time. I'm not sure how to make the test more reliable without using other synchronization primitives. But this test seems to be a test on a synchronization primitive, but it would be better to avoid using other synchronization primitives to test it... Well, I wrote the simplest workaround: increase timeouts. |
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
…GH-109875) Increase timeouts. Barrier default timeout should be long enough to spawn 4 threads on a slow CI. (cherry picked from commit e5186c3) Co-authored-by: Victor Stinner <vstinner@python.org>
GH-109876 is a backport of this pull request to the 3.12 branch. |
…GH-109875) Increase timeouts. Barrier default timeout should be long enough to spawn 4 threads on a slow CI. (cherry picked from commit e5186c3) Co-authored-by: Victor Stinner <vstinner@python.org>
GH-109877 is a backport of this pull request to the 3.11 branch. |
2 tests failed on Windows x86:
|
…#109875) Increase timeouts. Barrier default timeout should be long enough to spawn 4 threads on a slow CI.
…#109875) Increase timeouts. Barrier default timeout should be long enough to spawn 4 threads on a slow CI.
Increase timeouts. Barrier default timeout should be long enough to spawn 4 threads on a slow CI.