[ ci ] add 45 minute timeout to jobs running tests #3504
Merged
+4
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I do know that timeouts will just happen sometimes on these agents, even if
the task itself doesn't lock out. So this timeout is a very good idea even
if all the Idris related bugs are fixed
…On Fri, Feb 28, 2025, 13:06 Steve Dunham ***@***.***> wrote:
Description
We're having some CI runs freezing up during tests and being killed after
five hours. This has occurred a few times in macos-self-host-chez and in
windows-bootstrap-chez. I don't have a root cause, but suspect a bug in
chez or possibly the test runner is causing a deadlock. I see that there is
some history of deadlocks on these platforms in the chez bug tracker.
As a workaround, I've added a 45 minute timeout to the jobs that run
tests. The typically run in about half that time. They will still fail when
there is a deadlock, but will fail in 45 minutes instead of 5 hours.
------------------------------
You can view, comment on, or merge this pull request online at:
#3504
Commit Summary
- d39357b
<d39357b>
[ ci ] add 45 minute timeout to jobs running tests
File Changes
(1 file <https://github.com/idris-lang/Idris2/pull/3504/files>)
- *M* .github/workflows/ci-idris2-and-libs.yml
<https://github.com/idris-lang/Idris2/pull/3504/files#diff-5658ca7333819996e9571d9b9893a2b6c127639a3ad01de6424d8da3d9d85773>
(4)
Patch Links:
- https://github.com/idris-lang/Idris2/pull/3504.patch
- https://github.com/idris-lang/Idris2/pull/3504.diff
—
Reply to this email directly, view it on GitHub
<#3504>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2CKBD4UETEUQ6WW44KP6T2SCQTRAVCNFSM6AAAAABYC33RU2VHI2DSMVQWIX3LMV43ASLTON2WKOZSHA4DONZYGQ2DMOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We're having some CI runs freezing up during tests and being killed after five hours. This has occurred a few times in
macos-self-host-chezand inwindows-bootstrap-chez. I don't have a root cause, but suspect a bug in chez or possibly the test runner is causing a deadlock. I see that there is some history of deadlocks on these platforms in the chez bug tracker.As a workaround, I've added a 45 minute timeout to the jobs that run tests. The typically run in about half that time. They will still fail when there is a deadlock, but will fail in 45 minutes instead of 5 hours.