Cap the quality jobs so a hung runner cannot hold the release queue - #829
Merged
Merged
Conversation
A staging run's unit-test job hung at its first step and sat there for hours: no timeout-minutes meant GitHub's 6-hour default applied. Every later staging run then parked in docker-build's await_turn, which counts any older run still in flight, so one stuck runner stalled the whole release queue -- visible as "CI is stuck" with nothing failing. The caps are well above the real runtimes (lint ~20s, compile ~15s, unit ~30s, browser ~1m), so they only ever fire on a hang. Job names and ids are untouched: they are pinned as required checks on main. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
CI was stuck, not failing. Staging run 34708677330 hung on
Run unit testsat 17:35:48 and never moved -- the same step finishes in ~30s on every other run. With notimeout-minutes, GitHub's 6-hour default applied.docker-build.yml'sawait_turncounts any older run on the branch that is notcompleted, so every later staging push parked behind that one hung job. #827 sat atBLOCKEDwith all 18 checks green exceptWait for older merges to finish.I cancelled the hung run to unblock the queue. This caps the four quality jobs so the next hang fails in minutes instead of hours:
Job names and ids are untouched -- they are pinned as required checks on main.
🤖 Generated with Claude Code