Bound every CI job, so a hung one cannot hold the only runner #1066
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1066
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/bound-stuck-jobs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Partial fix for #930 — the half that is ours to fix.
That issue documents a task stuck in
runningfor over forty minutes while every other pull request waited behind it. With one runner, a hung job is not a slow job: it is a queue that has stopped, and it is indistinguishable from a queue that is merely busy. That is why #930 first looked like "pull_requestevents never create tasks" — at the moment of looking, nothing was moving.Every job now carries a bound:
test(×3 matrix)smokedockerA hang now costs ten minutes and returns the runner, instead of blocking the whole queue until someone notices. It does not make CI faster; it makes a failure cost minutes instead of an afternoon.
This does not close #930. The other half is throughput and
mainverification on merge, which needs either a second runner or a scheduler that works (see the note below) — neither of which is a code change in this repository.YAML validated:
test → 15,smoke → 10,docker → 10; theconcurrencyblock from #1060 is intact.Refs #930.