From 4d0e56f8f6b068948c9d4b5da17e6f1b48afd325 Mon Sep 17 00:00:00 2001
From: robobun <117481402+robobun@users.noreply.github.com>
Date: Thu, 13 Aug 2026 10:32:37 +0000
Subject: [PATCH] test: give worker-shutdown-post-leak an explicit 90s timeout

The test is ASAN-only. Under a debug+ASAN build on a loaded machine the
worker boot and VM teardown it spawns take 5-7s, so it times out at the
5s default, and when LSan does find a leak, symbolizing the report against
the debug binary needs several seconds more, so a real regression also
surfaced as a timeout with the report cut off. Same budget as the other
LSan guard tests (shell-worker-terminate-leak, spawn-stdin-pipe-fd-leak).
---
 .../js/node/worker_threads/worker-shutdown-post-leak.test.ts | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/test/js/node/worker_threads/worker-shutdown-post-leak.test.ts b/test/js/node/worker_threads/worker-shutdown-post-leak.test.ts
index b6b03722c6be..db07a3e95785 100644
--- a/test/js/node/worker_threads/worker-shutdown-post-leak.test.ts
+++ b/test/js/node/worker_threads/worker-shutdown-post-leak.test.ts
@@ -46,4 +46,9 @@ test.skipIf(!isASAN || isWindows)(
     const [stdout, stderr, exitCode] = await Promise.all([proc.stdout.text(), proc.stderr.text(), proc.exited]);
     expect({ stdout, stderr, exitCode }).toEqual({ stdout: "", stderr: "", exitCode: 0 });
   },
+  // Worker boot + VM teardown alone take ~5s under debug+ASAN on a loaded
+  // machine, and when LSan does find a leak, symbolizing the report against
+  // the debug binary adds several seconds more; the 5s default turned both
+  // into a timeout.
+  90_000,
 );