Repository navigation
ci: cancel superseded runs of bridge-gate, governance and hypatia-scan - #1045
Conversation
These three run on every PR push and had no concurrency group, so a newer push left the older run holding a runner. With many PR pushes at once (the 2026-11-09 16:12-16:23 burst) jobs waited about two hours, and tests.yml's Integration Coverage was abandoned unrun. The block is the one tests.yml already uses. Not changed, on purpose: label-triage.yml (issue events share one group, so one issue would cancel another's triage); mirror.yml, labels.yml and zz-one-off-lock-regen.yml (a cancel mid-run could leave a mirror, the label set or a pushed commit half done); rsr-oracle.yml (reusable; the caller owns concurrency); scorecard.yml (schedule and dispatch only). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZnmBahbhfkFEP6ark4
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 4 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
|
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |



Why
On 2026-11-09 between 16:12 and 16:23 UTC, 7 PR branches were pushed within about 10 minutes. Their runs waited about two hours for runners: created at 16:12, jobs started around 18:05. In
tests.yml, Integration Coverage never got a runner, soIntegration Statusreported it asabandonedand failed. Example: run 42652388070, where Build Test Images and Integration Tests passed and Integration Coverage has no job record.9 of the 37 workflows have no
concurrencygroup, so a newer push does not free the runner an older run holds.What
The block that
tests.ymlalready uses is added to the 3 workflows that run on every PR push and only read and report:bridge-gate.yml,governance.yml,hypatia-scan.yml.Left alone on purpose:
label-triage.yml: issue events share one group, so one issue would cancel another's triage.mirror.yml,labels.yml,zz-one-off-lock-regen.yml: a cancel mid-run could leave a mirror, the label set or a pushed commit half done.rsr-oracle.yml: a reusable workflow; its caller owns concurrency.scorecard.yml: schedule and dispatch only, so it never holds a PR runner.Testing
yq '.concurrency'parses on all three files. Nouses:line changed, soactions.lockis unaffected.Generated by Claude Code