rbrooks/Quest-Board

Watch

Fork 0

test(e2e): J6 gets a budget of its own, as J1 and J2 have #880

Closed

claude-bot wants to merge 0 commits from fix/j6-budget into main

claude-bot commented

2026-09-27 03:59:35 +00:00

Collaborator

J6 on the phone project timed out in #866's CI (run 11141). It failed on both attempts, at 60 s, with every step still making progress. This is a budget problem, not a race.

Evidence (from the run's trace artifact and job logs):

Where the time goes: in the failing phone attempt, no single step took more than about 2 s. About 32 s of the 60 went to J6's twelve axe scans (~2.7 s each on phone). The trace shows the test had reached its last act, the wiki, when time ran out.
Recent J6 phone timings: 26.1 s (11128, #866's own earlier run), 31.1, 45.5, 50.1 and 39.9 s (main, run 11136). So J6 was already running close to the default 60 s.
Only J6 moved. Every other phone test in 11141 was flat against main. J6's spec and fixtures are identical on #866 and main. Run 11141 ran alongside five other CI runs.

The fix: test.setTimeout(180_000), with a comment. J1's long test (240 s) and J2's serial block (180 s) already have budgets of their own for the same reason. The config's minute is for a page; J6 is a whole journey.

There's no changelog fragment, because nothing user-facing changes.

🤖 Generated with Claude Code

J6 on the phone project timed out in #866's CI (run 11141). It failed on both attempts, at 60 s, with every step still making progress. **This is a budget problem, not a race.** **Evidence** (from the run's trace artifact and job logs): - **Where the time goes:** in the failing phone attempt, no single step took more than about 2 s. About 32 s of the 60 went to J6's twelve axe scans (~2.7 s each on phone). The trace shows the test had reached its last act, the wiki, when time ran out. - **Recent J6 phone timings:** 26.1 s (11128, #866's own earlier run), 31.1, 45.5, 50.1 and 39.9 s (main, run 11136). So J6 was already running close to the default 60 s. - **Only J6 moved.** Every other phone test in 11141 was flat against main. J6's spec and fixtures are identical on #866 and main. Run 11141 ran alongside five other CI runs. **The fix:** `test.setTimeout(180_000)`, with a comment. J1's long test (240 s) and J2's serial block (180 s) already have budgets of their own for the same reason. The config's minute is for a page; J6 is a whole journey. There's no changelog fragment, because nothing user-facing changes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 1 commit

2026-09-27 03:59:36 +00:00

test(e2e): J6 gets a budget of its own, as J1 and J2 have

CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 57s

Details

CI / Bot tests and audit (pull_request) Successful in 2m3s

Details

CI / Backend lint (ruff) (pull_request) Successful in 31s

Details

CI / Bot/backend version sync (pull_request) Successful in 28s

Details

CI / Feedback site tests (pull_request) Successful in 48s

Details

CI / Docker image build (pull_request) Successful in 32s

Details

CI / Does this change touch the recording path? (pull_request) Successful in 15s

Details

CI / Synthetic session harness (no GPU, no LLM) (pull_request) Has been skipped

Details

CI / Frontend tests, audit, and build (pull_request) Successful in 20m51s

Details

CI / Backend migration, tests, and audit (pull_request) Successful in 41m50s

Details

CI / End-to-end journeys (desktop, phone, keyboard-only) (pull_request) Failing after 1h21m22s

Details

be5bb0af2c

J6 is five acts and twelve axe scans in one test. On the phone project it
has run 26-50 s on recent runs and ran past the default 60 s twice in a row
on #866 (run 11141), with every step still progressing: no single step over
2 s, and 32 s of the 60 in axe. The keyboard and desktop projects, and every
other phone test, were flat against main. A budget, not a race.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

rbrooks referenced this pull request from a commit

2026-09-27 06:24:54 +00:00

Merge fix/j6-budget (#880) into lane 9 page 4a

rbrooks referenced this pull request from a commit

2026-09-27 06:24:54 +00:00

Merge lane 9 page 4a (with main, #880, #882) into lane 8 PR 1

rbrooks referenced this pull request from a commit

2026-09-27 06:24:54 +00:00

Merge lane 8 PR 1 (with main, #880, #882) into lane 10 PR 2

rbrooks referenced this pull request from a commit

2026-09-27 06:24:56 +00:00

Merge lane 10 PR 2 (with #865's email fix, main, #880, #882) into lane 10 PR 6

claude-bot referenced this pull request

2026-09-27 06:25:12 +00:00

feat(bot,webapp): notifications out — DMs, the GM's warnings, email that reaches people (lane 10 PR 2) #865

claude-bot commented

2026-09-27 08:13:39 +00:00

Author

Collaborator

This commit (be5bb0af) landed on main as part of train 2, merged into #866's branch, which merged as 6773879c. This PR's own CI failure was the runner's browser crashing under load ("Target crashed" across unrelated journeys), not the change itself. Closing, since the change is already on main.

This commit (be5bb0af) landed on main as part of train 2, merged into #866's branch, which merged as 6773879c. This PR's own CI failure was the runner's browser crashing under load ("Target crashed" across unrelated journeys), not the change itself. Closing, since the change is already on main.

claude-bot closed this pull request

2026-09-27 08:14:02 +00:00