Skip to content

Stabilize flaky Vitest fixtures and parallel builds#17

Closed
aminevg wants to merge 3 commits intomainfrom
t3code/fix-flaky-tests
Closed

Stabilize flaky Vitest fixtures and parallel builds#17
aminevg wants to merge 3 commits intomainfrom
t3code/fix-flaky-tests

Conversation

@aminevg
Copy link
Copy Markdown
Contributor

@aminevg aminevg commented Mar 23, 2026

Summary

  • Isolate Vite cache directories per Vitest process to avoid ENOTEMPTY races when test suites run in parallel.
  • Stop cleaning shared fixture directories during teardown and rely on per-run output directories instead.
  • Increase Vitest timeouts and switch core tests to forks for better isolation.
  • Make the Hono CLI build test use a symlinked temporary build root to avoid conflicts in shared dist/ output.

Testing

  • Not run in this branch review.
  • Expected verification: pnpm build
  • Expected verification: pnpm run typecheck
  • Expected verification: pnpm run ci:biome
  • Expected verification: pnpm test

aminevg added 3 commits March 23, 2026 14:23
- isolate Vite cache dirs per run
- avoid shared dist cleanup in fixture teardown
- raise Vitest timeouts and use forked workers
- Simplify the build assertion formatting
- Normalize fixture config formatting for consistency
- Let Vitest use the default pool to reduce flaky test behavior
@aminevg aminevg closed this Mar 23, 2026
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.

1 participant