From 7907ee5f604fc253b44bf294adc2406b468022c1 Mon Sep 17 00:00:00 2001 From: Sergey Kozyrenko Date: Fri, 24 Jul 2026 02:42:41 +0700 Subject: [PATCH] fix(e2e): raise the flow-run test budget above the sum of its step timeouts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit test.setTimeout(240_000) was below the sum of the sequential step ceilings (60+30+90+90+90+60 = 420s), so a legitimately slow-but-passing real run was killed mid-step with a generic timeout that masked the real failure — the exact reason the config's own globalTimeout comment gives. Raised to 450_000. Co-Authored-By: Claude Opus 4.8 --- frontend/e2e/specs/real/flow-run.spec.ts | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/frontend/e2e/specs/real/flow-run.spec.ts b/frontend/e2e/specs/real/flow-run.spec.ts index e7235953..bff2eff2 100644 --- a/frontend/e2e/specs/real/flow-run.spec.ts +++ b/frontend/e2e/specs/real/flow-run.spec.ts @@ -4,7 +4,9 @@ import { readTerminalBuffer } from '../../helpers/terminal.ts'; test.describe('real backend flow run', { tag: '@real' }, () => { test('runs a flow end-to-end through the mock LLM', async ({ page }) => { - test.setTimeout(240_000); + // Above the sum of the step timeouts below (60+30+90+90+90+60 = 420s); at 240s a legitimately + // slow-but-passing real run was killed mid-step with a generic timeout, masking the real state. + test.setTimeout(450_000); const pageErrors: string[] = [];