From 1d857790dfb549a2ebfd27bf8acaac866b1f6d5f Mon Sep 17 00:00:00 2001 From: JUN Date: Tue, 6 Oct 2026 09:01:28 +0900 Subject: [PATCH] test(responses): keep the post-refresh replay inside the pacing window on Windows --- tests/responses/responses-pool-401-refresh.test.ts | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tests/responses/responses-pool-401-refresh.test.ts b/tests/responses/responses-pool-401-refresh.test.ts index 17da8c768be..4e1d10b50b6 100644 --- a/tests/responses/responses-pool-401-refresh.test.ts +++ b/tests/responses/responses-pool-401-refresh.test.ts @@ -812,7 +812,10 @@ describe("ordinary pool 401 refresh and replay (#2887)", () => { test("a post-refresh credit hold in the pacing queue does not announce a replay send", async () => { const cfg = config(); - cfg.providers.openai!.requestPacing = { enabled: true, minIntervalMs: 200 }; + // The replay must still be inside the pacing interval after the forced refresh. On hosted + // Windows runners refresh plus replay preparation takes several hundred ms, so 200 ms elapsed + // before the replay reached the queue and it was never observed as queued. + cfg.providers.openai!.requestPacing = { enabled: true, minIntervalMs: 2_000 }; const harness = installHarness(); let dispatchSignals = 0; const pending = handleResponses(request("/v1/responses"), cfg, { model: "", provider: "" } as RequestLogContext,