From 65b9cff299b4fddfeae026a89f87475b56379bfe Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Wed, 26 Aug 2026 17:56:43 +0000 Subject: [PATCH] fix: raise bun-polyfill subprocess budget to 60s for degraded Windows runners MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 50ms-sleep test blew the 20s budget on BOTH bun retry attempts on PR #2700's windows-latest runner (run 32989821401) — sustained AV/runner pressure, not just the documented cold-start. Same flake passed-on-rerun on the prompt-token-load-reduction branch yesterday. Budget only; every assertion still checks exact output. Co-Authored-By: Claude Fable 5 --- browse/test/bun-polyfill.test.ts | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/browse/test/bun-polyfill.test.ts b/browse/test/bun-polyfill.test.ts index 960c934b1..21ab985cb 100644 --- a/browse/test/bun-polyfill.test.ts +++ b/browse/test/bun-polyfill.test.ts @@ -3,8 +3,13 @@ import * as path from 'path'; // Every test here spawnSync's a `node` child; Windows CI cold-start (AV scan, // first-touch of node.exe) alone can blow bun's 5s default — observed 5,007ms -// on a 50ms sleep test. Subprocess budget, not assertion looseness. -setDefaultTimeout(20_000); +// on a 50ms sleep test. 20s was still not enough: on 2026-08-26 (PR #2700, +// run 32989821401) the 50ms sleep test blew 20s on BOTH bun retry attempts on +// a degraded windows-latest runner, so cold-start alone doesn't explain it — +// sustained AV/runner pressure does. Subprocess budget, not assertion +// looseness: every assertion still checks exact output, only the slowness +// allowance grows. +setDefaultTimeout(60_000); // Load the polyfill into a fresh object (don't clobber globalThis.Bun) const polyfillPath = path.resolve(import.meta.dir, '../src/bun-polyfill.cjs');