🤖 tests: localStorage budget worst-case test runs near the 5 s timeout and flakes in the merge queue
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- performance, testing-qa
Research direction
Start in src/browser/hooks/persistedStateBudget.test.ts at the "localStorage budget > the worst case of every registered key stays under the ceilings" test, and run it repeatedly with Bun. Determine whether the computation or timeout is the appropriate focus; done means the test completes reliably on CI runners without timing out or flaking.
Written by the indexing model from the issue text.
Description
Problem
src/browser/hooks/persistedStateBudget.test.ts > "localStorage budget > the worst case of every registered key stays under the ceilings" runs close to bun's default 5 s test timeout. In a merge-queue run it timed out: 5694 ms in Test / Unit (3/6), run 36632452163, job 109624872283. That removed #5243 from the queue even though the PR does not touch any localStorage key. Locally, on origin/main 2d841af315 plus #5243, the same test takes 3.3–4.6 s over 3 runs (bun 1.3.5).
The test landed with #5238.
Suggested fix
Either make the worst-case computation cheaper, or give this test an explicit timeout sized for CI runners.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $118.34
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 140
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 874
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 65/100
Maintainers usually reply within 1 day
-
bug investigation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
approved backlog
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
approved backlog
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
approved backlog
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day