Given tests: order arrivals by limiter state instead of sleeps (limiter, spread, cancel-while-queued)

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-25 11:20:26 -07:00
parent 6c3a2cff8a
commit 98faa3a57d
7 changed files with 46 additions and 24 deletions
@@ -12,8 +12,10 @@
 - **02-props-loaded-only** (to be written after v2 merges) — the poller asks `/props?model=X`
  only for models `/v1/models` lists as loaded, because llama-server's router autoloads a model
  named in that query (`models_autoload`). See the v2 README's note of 2026-09-25.
- **03-timing-margins** (to be written) — the remaining sleep-ordered assertions in v1 and v2
-  given tests move to state-based waits, as `TestQueueFullIs503` and `TestParallelAndQueue` did.
+- ~~03-timing-margins~~ — done by the owner directly (test-only work, no implementer task): the
+  remaining ordering sleeps in `limiter_test.go`, `proxy_test.go` and `cancel_test.go` now wait on
+  limiter state (`Queued`/`InFlight`); the one sleep left is a deliberate lower bound. Five clean
+  `-race` runs of both packages except the 499 defect task 01 fixes.

 **How this plan was made:** acceptance tests first; no reference implementation. The given test
 for task 01 was run against the v2 tree (fails six of six) and against a throwaway fix that