Relationships
≡ duplicate of #4740#4801 test: the command routes test still stalls at its 120 s worker deadline when it runs in its own deno test process
Opened by zack · 11/16/2026· Shipped 11/16/2026
What happens
integration/command_routes_rules_test.ts ('command routes: each route loads alone in a fresh module graph...') fails in verify-build with 'AssertionError: : no answer within 120000ms'. swamp-club#4711 (f64f54ecb) moved the file into a deno test process of its own (OWN_PROCESS_FILES in scripts/test_shards.ts), but it still stalls there.
Evidence (verify-build runs on branch issue-4763, which does not touch the CLI routes)
- shard 4 (the own-process shard): 'datastore: no answer within 120000ms', shard took 155s; the passing runs take 61 to 63s. verify-build ran alone on the host at the time.
- an earlier run: 'datastore quarantine: no answer within 120000ms' while verify-reviews ran in parallel.
- 2 of 5 verify-build runs on that branch failed this way; the same commit passes the test alone locally three times in 26 to 36s.
Expected
The test passes reliably in verify-build, or its stall is detected and retried rather than failing the run.
Notes
The #4711 write-up suspected a lost wakeup in module loading shared across Workers in one process; isolating the file from other Worker-heavy files was not enough, so the stall seems to happen within the ~100 Workers this test spawns itself.
Shipped
Click a lifecycle step above to view its details.