Relationships
↔ sibling #4793#4822 Test flake: team forwarding 'a leader that left two forwards in a row unanswered is refused at once' sometimes forwards and fails instead of refusing
Opened by stack72 · 11/16/2026· Shipped 11/17/2026
integration/serve_v3_team_forwarding_test.ts:263 "team forwarding: a leader that left two forwards in a row unanswered is refused at once, never sent, until a new leader takes over" fails intermittently in verify-build.
Seen: 6 failures in 144 recorded verify-build runs (counted from the main checkout's workflow-run logs, 2026-11-16). The latest was on the swamp-club#4784 branch (run 0ea21fa3) under host load (load average about 16), and that branch doesn't touch serve's leader forwarding.
Failure: the assertion sees serve_not_leader with the message "This swamp serve node forwarded the request to the leader, which changed or stopped answering before it replied…". That is the reply to a forward that was sent and went unanswered, where the test expects the request to be refused at once without being sent.
Likely cause: the "two forwards in a row unanswered" state isn't recorded before the next request is decided under load, so the third request is still forwarded. Either the circuit's state update races the next forward, or the test's second unanswered forward hasn't been counted when the third request starts, and should wait on that state rather than on time.
Shipped
Click a lifecycle step above to view its details.