-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
[tests] test_subprocess maybe avoid a timeout race condition? #133420
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
[tests] test_subprocess maybe avoid a timeout race condition? #133420
Conversation
The few buildbot failures on python#133103 are possibly just due to racing a child process launch and exit?
!buildbot .s390. |
🤖 New build scheduled with the buildbot fleet by @gpshead for commit 9063e79 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F133420%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
!buildbot .Server.2022. |
🤖 New build scheduled with the buildbot fleet by @gpshead for commit 9063e79 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F133420%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
It looks like the race is surfacing on Ubuntu freethreaded CI (e.g. https://github.com/python/cpython/actions/runs/14827808058/job/41623568354?pr=133365) so if it is fixed there that should be a good signal. |
The hypothesis failure looks similar to a failure I saw. I filed #133419 to track the |
Thanks @gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…GH-133420) The few buildbot failures on python#133103 are possibly just due to racing a child process launch and exit? (cherry picked from commit b64aa30) Co-authored-by: Gregory P. Smith <[email protected]>
GH-133421 is a backport of this pull request to the 3.13 branch. |
ops, sorry about this. Thanks for the patch! |
The few buildbot failures on #133103 are possibly just due to racing a child process launch and exit?