From 496765d6d9bac740ff7147b9f49ac5aca157ca2d Mon Sep 17 00:00:00 2001
From: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Date: Thu, 20 Aug 2026 12:53:24 -0700
Subject: [PATCH] shorten comments

---
 .../browser-cookie-import-partition.electron.test.ts       | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/src/main/browser/browser-cookie-import-partition.electron.test.ts b/src/main/browser/browser-cookie-import-partition.electron.test.ts
index 194ed9a4eb7..c686587a661 100644
--- a/src/main/browser/browser-cookie-import-partition.electron.test.ts
+++ b/src/main/browser/browser-cookie-import-partition.electron.test.ts
@@ -16,12 +16,7 @@ afterAll(() => {
   }
 })
 
-// Why: on CI runners this Electron launch intermittently never reaches `ready` — the fixture's
-// watchdog fires with its step still 'starting', and the same signature hits sibling cookie
-// fixtures on unrelated PRs, including one whose watchdog allows 20s. Measured off-runner, `ready`
-// costs ~0.1-0.4s even at a quarter CPU, so the launch is wedged rather than slow and no watchdog
-// value fixes it. Relaunch once, and only for that signature: every assertion, import failure, and
-// crash after `ready` still fails on the first attempt.
+// Retry once when Electron startup times out before `ready`; keep later failures fatal.
 const FIXTURE_LAUNCH_ATTEMPTS = 2
 
 function neverReachedElectronReady(fixtureResult: string): boolean {