From bf3910bdc0f1e63421840668ae94a0f5f41fedab Mon Sep 17 00:00:00 2001 From: Mohamed Boudra Date: Sat, 15 Aug 2026 12:30:17 +0000 Subject: [PATCH] test(workspaces): keep launch fixture alive --- .../app/e2e/browser/new-workspace-launch-memory.spec.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/packages/app/e2e/browser/new-workspace-launch-memory.spec.ts b/packages/app/e2e/browser/new-workspace-launch-memory.spec.ts index dc15ed981d..cf755b47fe 100644 --- a/packages/app/e2e/browser/new-workspace-launch-memory.spec.ts +++ b/packages/app/e2e/browser/new-workspace-launch-memory.spec.ts @@ -21,13 +21,13 @@ import { type TerminalProfileSeed, } from "../support/helpers/new-workspace-launch"; -// `sleep` keeps the terminal alive long enough for the UI to attach and -// render output before the process exits — see new-workspace-launch-terminal.spec.ts. +// Loaded CI workers can take several seconds to materialize the runtime and attach the UI. +// Keep the fixture bounded but alive through that assertion window. const PROMPT_PROFILE: TerminalProfile = { id: "e2e-memory-profile", name: "Memory Profile", command: "/bin/sh", - args: ["-c", 'echo remembered: "$0"; sleep 10', "{{{prompt}}}"], + args: ["-c", 'echo remembered: "$0"; sleep 60', "{{{prompt}}}"], }; function hasLeftNewWorkspaceRoute(url: URL): boolean {