From 56bebf3ea37ebd9e5bc6302f8726ce87a03eb1d5 Mon Sep 17 00:00:00 2001 From: LongYinan Date: Thu, 15 Oct 2026 16:06:26 +0800 Subject: [PATCH] test: give heavy wrapper tests a Windows timeout budget The "generateWrapper with migrations" tests bundle Workers and start workerd. On Windows CI runners they can stall on disk and process start and pass the 20-second unit timeout. Give that describe a 60-second budget on Windows only. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_0123r5HnanmW2VUrZ7VWDufH --- packages/void/test/unit/wrapper.test.ts | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/packages/void/test/unit/wrapper.test.ts b/packages/void/test/unit/wrapper.test.ts index d34ccdad6..b67080dfe 100644 --- a/packages/void/test/unit/wrapper.test.ts +++ b/packages/void/test/unit/wrapper.test.ts @@ -502,7 +502,10 @@ describe('generated wrapper queue dispatch', () => { }); }); -describe('generateWrapper with migrations', () => { +// These tests bundle Workers and start workerd. Windows CI runners stall on disk and process start, +// so one test can take 20 seconds there. Keep the longer budget local to these tests. +const migrationTestTimeout = process.platform === 'win32' ? 60_000 : undefined; +describe('generateWrapper with migrations', { timeout: migrationTestTimeout }, () => { const roots: Array = []; // Each new PGlite runs initdb, which can take seconds on CI. Run it once in this hook, with its // own budget; each PostgreSQL test loads a fresh database from the initialized data directory.