You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
e2e-gate --status success filter hides re-run-to-green Runtime Live E2E runs from the release gate (#460)
* e2e-gate: drop --status success from ghRunListForCommit
At the v0.23.0 cut, gh run list --status success returned [] for a run
re-run to green minutes earlier (conclusion success, attempt 2), while
the same query without --status already saw the success -- the filter
lags conclusion right after a re-run, blocking a genuinely green cut.
The parked-run defense the flag was meant to provide already lives in
EvaluateE2EGate's predicate (empty conclusion never matches), so the
flag was redundant and only cost re-run-to-green cuts.
T1 drives the real ghRunListForCommit against a fake gh shim pinning
the gate-time observation (RED under --status, GREEN once dropped).
T2 confirms the parked-run defense survives the flag's removal.
* e2e-gate test: pin --workflow "Runtime Live E2E" as the query's live-matrix binding
Cycle-1 audit finding: workflowName is not among ghRunListForCommit's
fetched --json fields, so the --workflow "Runtime Live E2E" argv token
is the ONLY thing binding the release gate to the live matrix. Dropping
it left the whole suite green -- any green run on the release commit
(e.g. ordinary push CI) would then satisfy the gate.
The gh shim now returns [] unless argv carries that exact --workflow
"Runtime Live E2E" pair, so the token's removal fails the gate closed
in the test. Verified locally: removing the token from
ghRunListForCommit flips TestE2EGateCommandPassesOnRerunToGreenLiveRun
RED (exit 1, "no conclusion:success..."); reverting restores GREEN.
---------
Co-authored-by: Spike Test <spike@example.com>
0 commit comments