From 6683ee8c30489a24fc9c04fb7bc1e49f74fdbace Mon Sep 17 00:00:00 2001 From: SnapOtter Date: Mon, 29 Jun 2026 23:46:59 +0800 Subject: [PATCH] test: clear the sync-wait floor in the format matrix per-case timeout (#381) The matrix per-case timeout equaled the 30s SYNC_WAIT_MS test floor, so a contended job that rode the full sync-wait window before returning a valid 202 raced the timeout and was flagged as a hang. Raise it to 60s. extract-pages on tiny.pdf took 30051ms in the PR run, just over the old 30000ms limit. --- .../integration/generated/format-matrix-multimodal.test.ts | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/tests/integration/generated/format-matrix-multimodal.test.ts b/tests/integration/generated/format-matrix-multimodal.test.ts index 15ffeaeb..d4d12cc1 100644 --- a/tests/integration/generated/format-matrix-multimodal.test.ts +++ b/tests/integration/generated/format-matrix-multimodal.test.ts @@ -177,6 +177,10 @@ describe("multi-modality tool x format matrix", () => { describe(toolId, () => { for (const fixture of effectiveFixtures) { + // 60s per-case timeout clears the 30s SYNC_WAIT_MS test floor (per-fork-env.ts): + // under load a contended docs/media job can ride the full sync-wait window and + // return a valid 202 (which this matrix accepts), so the timeout must sit above + // that floor or a slow-but-valid job is wrongly flagged as a hang. it(`${fixture.filename} -> clean status`, async () => { const content = readFileSync(join(fixture.dir, fixture.filename)); const settings = defaultSettingsFor(toolId); @@ -281,7 +285,7 @@ describe("multi-modality tool x format matrix", () => { `${toolId} x ${fixture.filename}: 501 without error/code`, ).toBeDefined(); } - }, 30_000); + }, 60_000); } }); }