From 94b1ff99dd454a8ebff85e5e6e12b3e643d2a089 Mon Sep 17 00:00:00 2001
From: "gfargo-horizon-agent[bot]"
 <294710345+gfargo-horizon-agent[bot]@users.noreply.github.com>
Date: Mon, 27 Jul 2026 03:21:34 +0000
Subject: [PATCH] fix(test): raise tree-sitter WASM init timeout for slow CI
 runners

The `.wasm-backed` tree-sitter parser suite pays the one-time
`Parser.init` bootstrap cost on its first real test. Jest's default
5000ms budget was tight enough that the macOS CI runner (Node
22.22.2) intermittently exceeded it, unrelated to the runner's own
logic. Bump the suite timeout to 20000ms to absorb cold-start
variance.
---
 .../default/__tree_sitter__/tsTreeSitterParser.test.ts      | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/lib/parsers/default/__tree_sitter__/tsTreeSitterParser.test.ts b/src/lib/parsers/default/__tree_sitter__/tsTreeSitterParser.test.ts
index 2a44015c..dfd6ad02 100644
--- a/src/lib/parsers/default/__tree_sitter__/tsTreeSitterParser.test.ts
+++ b/src/lib/parsers/default/__tree_sitter__/tsTreeSitterParser.test.ts
@@ -36,6 +36,12 @@ describeWithWasm('treeSitterTsParser (.wasm-backed)', () => {
   // race the init promise. The init failure path is now retry-friendly
   // (see `ensureRuntime` in runtime.ts), and we trust the first test in
   // this suite to exercise the init path cleanly.
+  //
+  // The one-time `Parser.init` WASM bootstrap can exceed jest's default
+  // 5000ms on a loaded/slow CI runner (observed on macOS runners); bump
+  // the suite timeout so a slow cold start doesn't fail an otherwise
+  // passing assertion.
+  jest.setTimeout(20000)
 
   it('returns undefined for non-TS / non-JS file paths', async () => {
     expect(await treeSitterTsParser.summarize(fileDiff('README.md', '+x'))).toBeUndefined()