Relationships
#4973 serve HTTP action follower test flakes: one person's rate limit through a follower can fail with 'the caller reached the limit'
Opened by zack · 11/20/2026· Shipped 11/20/2026
integration/serve_http_action_follower_test.ts, the test named: one person's rate limit through a follower leaves another's alone (around line 608), failed once in a full verify-build run (5 test shards, 8 jobs each) with AssertionError: the caller reached the limit, at line 618. The same commit passed the file 3 of 3 times when run alone, and four earlier full runs of nearly identical trees passed it. The failing branch changed no serve or rate-limit code. Likely a timing or shared-state race under load: the caller may not reach its limit before the assertion, or rate-limit state from another test in the shard leaks in (AGENTS.md asks tests authenticating as a fixed principal to call resetRateLimitState first). Verify-build run id: 6c1e8b03-419a-4089-b8ec-52187e3e9149.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.