Skip to content

test: Give the reviews mark-viewed test a 15s budget - #536

Merged
Ziinc merged 1 commit into
mainfrom
claude/reviews-viewed-timeout
Sep 26, 2026
Merged

Ziinc merged 1 commit into
mainfrom
claude/reviews-viewed-timeout

Conversation

@Ziinc

@Ziinc Ziinc commented Sep 26, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

test/integration/workspace/reviews.test.tsx > is able to mark a file as viewed and back to unviewed fails intermittently with Test timed out in 5000ms. It failed CI on #521, a PR that does not touch that code path.

  • The test sets up a repo and workspace, renders the Dashboard and does two Viewed round trips through the Rust backend, all inside the default 5s testTimeout (vitest.integration.base.ts).
  • When the machine is idle it takes about 1.6–2.7s. Under CPU contention it sometimes runs past 5s.
  • It fails the same way on main: 2 of 5 local runs while another suite was running.

Fix

Give the test an explicit 15_000 budget, the same as the other heavy Dashboard integration tests (for example remote-workspace-ui.test.tsx).

Verification

With every core busy, the file failed 1 of 4 runs before this change and passed 6 of 6 after it; the viewed test took 2.0–2.8s. lint and format are clean.
Generated by Claude Code

"is able to mark a file as viewed and back to unviewed" sets up a repo
and workspace, renders the Dashboard and does two Viewed round trips
through the Rust backend inside the 5s default testTimeout. Under CPU
contention (CI runners, or a local run beside another suite) it
intermittently runs past 5s, failing unrelated PRs, and fails the same
way on main. Match the explicit 15s budget the other heavy Dashboard
integration tests use.
@Ziinc
Ziinc merged commit ddc7865 into main Sep 26, 2026
16 checks passed
@Ziinc
Ziinc deleted the claude/reviews-viewed-timeout branch September 26, 2026 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants