From db64ddb58eef6aebd0874bcdaad266ca8f6205a0 Mon Sep 17 00:00:00 2001
From: kshitijk4poor <82637225+kshitijk4poor@users.noreply.github.com>
Date: Tue, 15 Sep 2026 00:58:00 +0530
Subject: [PATCH] test(desktop): widen the execProbe event-loop test timeout

The 'execProbe keeps the parent event loop available' case asserts nothing
about timing; the 1s spawn budget only exists so a wedged child cannot stall
the run. A cold Windows CI runner can take longer than 1s just to start the
node child, which failed the test for reasons unrelated to what it guards.
5s keeps the safety bound without the flake.
---
 apps/desktop/electron/backend-probes.test.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/desktop/electron/backend-probes.test.ts b/apps/desktop/electron/backend-probes.test.ts
index 299e2b2dbe..950ff81532 100644
--- a/apps/desktop/electron/backend-probes.test.ts
+++ b/apps/desktop/electron/backend-probes.test.ts
@@ -66,7 +66,7 @@ test('execProbe keeps the parent event loop available to the child', async () =>
   try {
     await execProbe(NODE_BIN, ['-e', childScript], {
       stdio: 'ignore',
-      timeout: 1_000,
+      timeout: 5_000,
       windowsHide: true
     })
   } finally {