mirror of
https://github.com/ranxianglei/billion-context.git
synced 2026-11-23 01:58:16 +08:00
The test job needs 9 guards; 4 are pull_request-only (version/kernel/ pi-subagents/lane-guard). A skipped need cascades the skip to dependents (GitHub-documented behavior) — the workflow comment's 'skipped needs count as satisfied' never held. Result: every master push ran CI with 'test: skipped' (e.g. run 38665531939), so master has had NO post-merge unit-test signal — the hole that let #3145 (port collisions), #3027 (golden drift) and #3035 slip red to master unnoticed. Fix: explicit 'if: !failure() && !cancelled()' on the test job: - pull_request: guards run; a guard failure still skips the legs (required checks pending, merge blocked — #2637 fail-fast tiering intact) - push/dispatch: PR-only guards skip harmlessly, the 12 shard legs RUN and master gets a real post-merge signal Cost: bounded by the existing per-ref concurrency cancel (owner-approved 2026-10-10) — rapid merge sequences only pay for the last push.