From 6a964f73944b98a2ec65ca7527472f8c8f14c567 Mon Sep 17 00:00:00 2001 From: Lacy Morrow Date: Mon, 20 Jul 2026 08:51:10 -0400 Subject: [PATCH] fix(test): raise core Git suite timeout to 30s on all hosted runners (LAC-2770) The `Git > clones a remote and reads checkout metadata` test hit bun's 5s default per-test timeout on `unit (windows)` on the dev merge commit 98fbeda13a. LAC-2717 raised timeouts on project-copy / repository-cache / snapshot but git.test.ts still carried the default, so the clone test (and its `Git worktrees` / `Git trees` siblings) remained exposed to the same GitHub-hosted Windows runner slowness. Apply the same pattern as LAC-2717: pass `{ timeout: 30_000 }` to the single `testEffect(...)` in git.test.ts. This covers all three describe blocks in one line. --- packages/core/test/git.test.ts | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/packages/core/test/git.test.ts b/packages/core/test/git.test.ts index f77e32fd8bab..bd8ec14789f2 100644 --- a/packages/core/test/git.test.ts +++ b/packages/core/test/git.test.ts @@ -10,7 +10,11 @@ import { branch, commit, gitRemote } from "./fixture/git" import { tmpdir } from "./fixture/tmpdir" import { testEffect } from "./lib/effect" -const it = testEffect(LayerNode.compile(Git.node)) +// These tests spawn real git subprocesses (init, clone, worktree add, +// diff/tree writes). On GitHub-hosted Windows runners each op costs +// 100ms-2.8s under full-suite load, exceeding bun's 5s default per-test +// timeout (LAC-2770 clone timeout; same shape as LAC-2717). +const it = testEffect(LayerNode.compile(Git.node), { timeout: 30_000 }) describe("Git", () => { it.live("clones a remote and reads checkout metadata", () =>