-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
gh-132912: Set 15 min timeout on GHA Hypothesis CI #132914
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
vstinner
commented
Apr 25, 2025
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: test_remote_pdb hangs randomly #132912
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
timeout-minutes
is currently set to 60. Lowering to 20/30 would make sense.
When you're done making the requested changes, leave the comment: |
I chose the middleground: 15 minutes :-) Other GHA jobs use the fast CI option, so 10 minutes. |
Ah, I misunderstood: the intent is to set a 15-minute per-test timeout. Keeping the overall at 60 makes more sense then, though recent runs have completed in under 10 minutes, so we could consider lowering to e.g. 30m. Are there any other GHA / CI jobs that don't use a per-test timeout value or A |
Would you mind to change your review? You requested changes and now the PR is marked as "Unresolved review". |
Aha, the change worked as expected on the Hypothesis CI. It displays the traceback where the test hangs:
|
Yes, there are other CI jobs running tests with no timeout:
But I don't know these CIs, so I prefer to leave them unchanged for now. |
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
GH-132937 is a backport of this pull request to the 3.13 branch. |