From 15ddf087c0a1ed799521f496202d8357f1325776 Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Sat, 15 Aug 2026 11:30:35 -0700 Subject: [PATCH] test: free-runner wall timeout 15min -> 6min (faster wedge diagnosis) The suite completes in ~100-160s; a wedge used to mean 15 minutes of silence before the kill-and-name epilogue fired. 6min keeps ~3.5x headroom over the slowest observed clean run while naming wedge suspects in minutes. --wall-timeout overrides per run. Co-Authored-By: Claude Fable 5 --- scripts/test-free-shards.ts | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/scripts/test-free-shards.ts b/scripts/test-free-shards.ts index b8744528e..40106d2c7 100755 --- a/scripts/test-free-shards.ts +++ b/scripts/test-free-shards.ts @@ -195,7 +195,11 @@ export const FREE_TEST_TIMEOUT_MS = 30_000; // full-suite --parallel invocation). A wedged child — a spinning main thread // no in-process --timeout timer can interrupt — is SIGKILLed at the group // level and reported 'timed-out', distinct from 'failed'. -export const DEFAULT_WALL_TIMEOUT_MS = 15 * 60_000; +// ~3.5x the observed full-suite wall (~100-160s). A wedged run should be +// killed-and-diagnosed (the epilogue prints the in-flight suspects) in +// minutes, not sat out — 15min of silence was pure diagnosis latency. +// Override per run with --wall-timeout . +export const DEFAULT_WALL_TIMEOUT_MS = 6 * 60_000; export function normalizeRelativePath(filePath: string): string { return filePath.replace(/\\/g, '/');