Repository navigation
test: event-driven first-chunk wait in the retired-stall-guard case (windows CI flake) - #3457
ranxianglei wants to merge 1 commit into
Conversation
…3449) A loaded windows runner delivered the first SSE byte slower than the fixed 2s wall-clock window, failing 'first chunk should have flowed through' on master itself (job 117073924654, case took 64.8s under concurrent-instance load). Wait for the first data event up to 15s instead, then observe >=2s of post-first-chunk silence before the negative assertions — the behavioral pin (retired guard must not cut or terminate a silent stream) is unchanged and a real pre-first-byte hang still fails at the deadline.
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4073-pr.3457.5c104feThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3457.tgz
npm install -g packageInstall instructions are refreshed on each push. |
|
(ai: vllm-qwen/qwen3.8-27b) Closing as duplicate of #3421 (which closed #3420): while this PR was in flight, #3421 merged to master ( |
What
The
retired stall guard: mid-stream silence survives any short window even with the stale export set (#1706/#1714)case intests/issue1452-socket-hardening.test.tswaited a FIXED 2000ms wall-clock window and then asserted the first SSE byte had arrived. On a loaded windows runner (masterce9bc90a3, job 117073924654,test (windows-latest, 24, 2)) first-byte delivery took longer than that window with no product defect involved — the case ran 64.8s under concurrent-instance load (multiple#394"another bili instance is running" warnings in the same run) and failedfirst chunk should have flowed through. The sibling behavioral pins (idle budget cuts at ~3s; startup notice names the stale export) passed in the same run.Fix
Replace the fixed window with an event-driven wait for the first data event (deadline 15s — the pattern this file already uses in the clientError-backstop case), then observe >=2s of post-first-chunk silence before the negative assertions.
Behavior change disclosure (test semantics only)
Verification
node --import tsx --test tests/issue1452-socket-hardening.test.ts→ 10/10 pass.npm run typecheckclean.Closes #3449