Skip to content

Double the test timeout on Windows CI runners #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HelloThisWorld merged 1 commit into from
Aug 18, 2026
Merged

Double the test timeout on Windows CI runners #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion vitest.config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,15 @@ export default defineConfig({
// The v0.3 execution tests are process-level integration tests (git
// snapshots, runner subprocesses, verification commands); slow CI
// runners regularly exceed the 5s default.
testTimeout: 30_000,
//
// Windows CI gets double the budget: process spawn costs several times
// more there, and with a second worker running the subprocess-heavy
// v1.2 driver suites, the git-heaviest single test (resume.test.ts
// "recovers each intermediate phase" — five git-initialized fixtures,
// ~50 blocking git spawns) ran out of its 30s on the 4-vCPU runner
// while 1,647 of 1,648 tests passed. A timeout is a slowness budget,
// not a correctness assertion; local runs and Linux/macOS stay tight.
testTimeout: process.env['CI'] !== undefined && process.platform === 'win32' ? 60_000 : 30_000,
maxWorkers: workerCeiling(),
pool: poolForPlatform(),
// On CI the default reporter writes a line per test to a non-TTY stream
Expand Down
Loading