-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
gh-120039: Reduce expected timeout in test_siginterrupt_off #120047
Conversation
The process is expected to time out. In the refleak builds, `support.SHORT_TIMEOUT` is often five minutes and we run the tests six times, so test_signal was taking >30 minutes.
🤖 New build scheduled with the buildbot fleet by @colesbury for commit f88aceb 🤖 If you want to schedule another build, you need to add the 🔨 test-with-refleak-buildbots label again. |
Lib/test/test_signal.py
Outdated
@@ -698,7 +698,7 @@ def handler(signum, frame): | |||
@unittest.skipUnless(hasattr(os, "pipe"), "requires os.pipe()") | |||
class SiginterruptTest(unittest.TestCase): | |||
|
|||
def readpipe_interrupted(self, interrupt): | |||
def readpipe_interrupted(self, interrupt, timeout): |
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.
In 2 of 3 cases the value is support.SHORT_TIMEOUT
, so you can make it the default value to reduce the diff.
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.
LGTM.
Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
…thonGH-120047) The process is expected to time out. In the refleak builds, `support.SHORT_TIMEOUT` is often five minutes and we run the tests six times, so test_signal was taking >30 minutes. (cherry picked from commit d419d46) Co-authored-by: Sam Gross <colesbury@gmail.com>
GH-120060 is a backport of this pull request to the 3.13 branch. |
…thonGH-120047) The process is expected to time out. In the refleak builds, `support.SHORT_TIMEOUT` is often five minutes and we run the tests six times, so test_signal was taking >30 minutes. (cherry picked from commit d419d46) Co-authored-by: Sam Gross <colesbury@gmail.com>
GH-120061 is a backport of this pull request to the 3.12 branch. |
…thon#120047) The process is expected to time out. In the refleak builds, `support.SHORT_TIMEOUT` is often five minutes and we run the tests six times, so test_signal was taking >30 minutes.
…thon#120047) The process is expected to time out. In the refleak builds, `support.SHORT_TIMEOUT` is often five minutes and we run the tests six times, so test_signal was taking >30 minutes.
…thon#120047) The process is expected to time out. In the refleak builds, `support.SHORT_TIMEOUT` is often five minutes and we run the tests six times, so test_signal was taking >30 minutes.
The process is expected to time out. In the refleak builds,
support.SHORT_TIMEOUT
is often five minutes and we run the tests six times, so test_signal was taking >30 minutes.test_siginterrupt_off
unnecessarily takes 30 minutes in refleak test #120039