-
-
Notifications
You must be signed in to change notification settings - Fork 32k
test_siginterrupt_off
unnecessarily takes 30 minutes in refleak test
#120039
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
Comments
colesbury
added a commit
to colesbury/cpython
that referenced
this issue
Jun 4, 2024
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.
colesbury
added a commit
that referenced
this issue
Jun 4, 2024
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.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 4, 2024
…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 <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 4, 2024
…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 <[email protected]>
This was referenced Jun 4, 2024
colesbury
added a commit
that referenced
this issue
Jun 4, 2024
…H-120047) (#120061) 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 <[email protected]>
colesbury
added a commit
that referenced
this issue
Jun 4, 2024
…H-120047) (#120060) 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 <[email protected]>
barneygale
pushed a commit
to barneygale/cpython
that referenced
this issue
Jun 5, 2024
…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.
noahbkim
pushed a commit
to hudson-trading/cpython
that referenced
this issue
Jul 11, 2024
…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.
estyxx
pushed a commit
to estyxx/cpython
that referenced
this issue
Jul 17, 2024
…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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
The
test_siginterrupt_off
test intest_signal
expects a timeout and usessupport.SHORT_TIMEOUT
.In at least some of the refleak test runners:
support.SHORT_TIMEOUT
to five minutesSo the test always takes a minimum of 30 minutes.
cpython/Lib/test/test_signal.py
Line 749 in e69d068
cpython/Lib/test/test_signal.py
Lines 775 to 781 in e69d068
Linked PRs
The text was updated successfully, but these errors were encountered: