From 62c3e5ef5d481bd73789ba6af510b9b24b8989b2 Mon Sep 17 00:00:00 2001 From: Craigory Coppola Date: Sat, 29 Aug 2026 23:02:23 -0400 Subject: [PATCH] fix(core): raise the nx package vitest timeout to cover the graph recompute spec project-graph-incremental-recomputation.spec.ts times out at exactly 35000ms on CI on every run that actually executes it: three runs in a row clipped at 35,009 / 35,018 / 35,070ms. Measured with the limit raised, the slowest test needs 42.4s on CI hardware, and its neighbours land at 32s and 29s. Locally the same test swings between 7s and 23s depending on pool load, so a 35s ceiling is inside the spec's own variance once CI's roughly 5x slowdown is applied. Master rarely shows it because most commits do not touch packages/nx and nx:test is served from cache. Any branch that busts that cache runs the spec every push and hits the limit. The jest preset carried the same 35s before the vitest move, so this is not a transform regression; the spec has been close to the line for a while and only surfaces on branches that execute it repeatedly. --- packages/nx/vitest.config.mts | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/packages/nx/vitest.config.mts b/packages/nx/vitest.config.mts index ec7b0756f35..ae9a3c61aae 100644 --- a/packages/nx/vitest.config.mts +++ b/packages/nx/vitest.config.mts @@ -56,7 +56,11 @@ export default defineConfig({ include: ['**/*.spec.ts'], exclude: ['src/native/tui/**', '**/node_modules/**'], setupFiles: ['./vitest.setup.mts'], - testTimeout: 35000, + // project-graph-incremental-recomputation.spec.ts stands up real native + // watchers and graph recomputes; its slowest test measured 42.4s on CI + // against the previous 35s limit, and the same test swings 7-23s locally + // depending on pool load. 90s clears the measured worst case by 2x. + testTimeout: 90_000, // Native .node bindings are not thread-safe across vitest worker threads. pool: 'forks', // Specs that stand up native workspace contexts leave their worker slow to