🤖 tests: flaky UI tests lifecycle archive-list and review focus fail the merge queue
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #7456 by @ThomasK33 — merged
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react, typescript
Research direction
Start with the two failing tests named in the issue: tests/ui/workspaces/lifecycle.test.ts and tests/ui/review/focus.test.ts. Run each test under conditions that reproduce the CI timing failure, then inspect its UI interactions and assertions. Done means both tests pass reliably under CI load and the merge queue no longer reports these failures.
Written by the indexing model from the issue text.
Description
Two UI integration tests failed in the merge queue on 2026-10-24 and took the 8-PR turn-engine stack (#7407 to #7414) out of the queue. Neither test touches the changed code (StreamManager internals), and both pass locally on the same top commit, 2 of 2 runs.
tests/ui/workspaces/lifecycle.test.ts: "Workspace Archive List Reactivity (UI) › newly archived workspace appears immediately in archive list after archiving from workspace view" failed withArchive button not found in menu. Merge-group run 40132426538, job 120986834301 (Test / Integration (1/3)).tests/ui/review/focus.test.ts: "ReviewPanel focus (UI + ORPC) › Cmd/Ctrl+2 focuses the review panel so j/k navigation works without clicking" failed withReview panel not focused. Merge-group run 40132429963, job 120986849933 (Test / Integration (2/3)).
Both look timing-dependent under CI load (a menu item or focus that is not there yet when the assertion runs). Merge-group Integration jobs failed in at least 8 runs on 2026-10-24.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $48.32
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 140
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 952
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/xum
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grafana/profiles-drilldown#1212 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
grafana/traces-drilldown#980 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openremote/openremote#3487 · 1 comment ·
-
triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
garrytan/gbrain#7635 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
coollabsio/jean#867 ·
Maintainers usually reply within 1 day