From c5cd8725aff7fa3fd5f8d4803cdc5d5ec4015c04 Mon Sep 17 00:00:00 2001 From: haelyra <49814733+haelyra@users.noreply.github.com> Date: Sun, 9 Aug 2026 18:38:59 -0400 Subject: [PATCH] test(install): scale uninstall CLI timeout for Windows CI The uninstall cases run two full CLI passes (install, then uninstall) over several hundred files under a flat 30s timeout, which is tight enough on Windows CI to fail intermittently with spawnSync ETIMEDOUT. install-apply.test.js already scales its timeout by platform for the same reason; match that precedent rather than re-running past the flake. Co-Authored-By: Claude Fable 5 --- tests/scripts/uninstall.test.js | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tests/scripts/uninstall.test.js b/tests/scripts/uninstall.test.js index 69d851e3b..030a4ba83 100644 --- a/tests/scripts/uninstall.test.js +++ b/tests/scripts/uninstall.test.js @@ -17,7 +17,10 @@ const CURRENT_PACKAGE_VERSION = JSON.parse( const CURRENT_MANIFEST_VERSION = JSON.parse( fs.readFileSync(path.join(REPO_ROOT, 'manifests', 'install-modules.json'), 'utf8') ).version; -const CLI_TIMEOUT_MS = 30000; +// Windows CI file I/O is several times slower, and these cases run two full +// CLI passes (install, then uninstall) over hundreds of files. install-apply +// tests already scale their timeout the same way. +const CLI_TIMEOUT_MS = process.platform === 'win32' ? 90000 : 30000; const { createInstallState, writeInstallState,