Skip to content

test(responses): keep the post-refresh replay inside the pacing window on Windows #6652

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lidge-jun merged 1 commit into from
Oct 6, 2026
Merged

test(responses): keep the post-refresh replay inside the pacing window on Windows #6652

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion tests/responses/responses-pool-401-refresh.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down
Loading