From 3fb0ab743532103c7040aa810afc52b24ef2878c Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Mon, 2 Mar 2026 15:11:14 +0000 Subject: [PATCH] test(perf): tighten cron issue-regression timeout windows --- src/cron/service.issue-regressions.test.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/cron/service.issue-regressions.test.ts b/src/cron/service.issue-regressions.test.ts index f74ccf2bb44..52c1bc3ae23 100644 --- a/src/cron/service.issue-regressions.test.ts +++ b/src/cron/service.issue-regressions.test.ts @@ -27,7 +27,7 @@ const noopLogger = { trace: vi.fn(), }; const TOP_OF_HOUR_STAGGER_MS = 5 * 60 * 1_000; -const FAST_TIMEOUT_SECONDS = 0.003; +const FAST_TIMEOUT_SECONDS = 0.0025; type CronServiceOptions = ConstructorParameters[0]; function topOfHourOffsetMs(jobId: string) { @@ -1526,7 +1526,7 @@ describe("Cron issue regressions", () => { const timerPromise = onTimer(state); const startTimeout = setTimeout(() => { bothRunsStarted.reject(new Error("timed out waiting for concurrent job starts")); - }, 120); + }, 90); try { await bothRunsStarted.promise; } finally { @@ -1556,7 +1556,7 @@ describe("Cron issue regressions", () => { // Keep this short for suite speed while still separating expected timeout // from the 1/3-regression timeout. - const timeoutSeconds = 0.012; + const timeoutSeconds = 0.01; const cronJob = createIsolatedRegressionJob({ id: "timeout-fraction-29774", name: "timeout fraction regression",