← Back to list
01Issue
BugShippedSwamp CLIPublic
AssigneesNone
Relationships
↔ sibling #4599#4595 fan-out: a failed run can end with its canary gate still pending, so a plain retry is refused with a hint naming the gate
Opened by stack72 · 11/10/2026· Shipped 11/10/2026
Found by the fan-out gates model test (integration/fleet_fan_out_gates_property_test.ts) while extending it for swamp-club#4562.
Repro (fleet harness, offline: fail, rollout batches [1, 100%], approve [canary], one step apply, both workers failing):
- Run: the canary w-1 fails, the canary gate waits. Approve it and resume: w-2 runs and fails. Run is failed.
- Disconnect w-2.
- Retry with --from apply. No lane is kept, so the canary gate is reset to pending. The canary re-runs and fails; w-2 is offline so its lane fails unstarted. No lane is left for the gate to hold, so the gate is never asked and never settled.
- The run ends failed with patch[approve-canary] still pending.
- A plain retry is refused: Step patch[approve-canary] in job patch is pending; retry needs every step finished. Add --from 'patch[approve-canary]' to run it.
Expected: a gate the run ends without asking is settled (skipped like a gate held by a halt), so the failed run is retryable; and the hint never names a gate as a --from step, since --from takes an authored step.
The model test currently mirrors this behaviour (a plain retry is refused while a gate is pending) so it stays green; when this is fixed that line of the model goes.
02Bog Flow
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse
Sign in to post a ripple.