fix(e2e): raise the flow-run test budget above the sum of its step timeouts

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 <noreply@anthropic.com>
This commit is contained in:
Sergey Kozyrenko
2026-07-24 02:42:41 +07:00
co-authored by Claude Opus 4.8
parent 3e4316e53c
commit 7907ee5f60
+3 -1
View File
@@ -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[] = [];