[GH-ISSUE #150] Unhandled coverage ENOENT in Vitest when test run has failures/retries #98

Closed
opened 2026-10-15 18:21:06 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Jul 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/150

npm test currently produces an unhandled Vitest coverage error after test failures/retries.

Observed in local run:

  • After process-capture failures/timeouts, suite exits with:
    • Unhandled Rejection
    • Error: Something removed the coverage directory "/root/rea/coverage/.tmp"
    • ENOENT: no such file or directory, open '/root/rea/coverage/.tmp/coverage-1.json'

Config contributing context:

  • vitest.config.ts sets coverage.enabled: true and default reporter/paths.
  • No explicit coverage.reportsDirectory override.

Impact:

  • CI noise after failures and potential instability when rerunning/retrying tests.

Suggested fix:

  • Set a fixed stable coverage temp path per run/worker or disable shared temp cleanup during retries.
  • Option: add a per-run coverage.reportsDirectory under tmpdir() or configure retry-safe cleanup.
Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/150 `npm test` currently produces an unhandled Vitest coverage error after test failures/retries. Observed in local run: - After process-capture failures/timeouts, suite exits with: - `Unhandled Rejection` - `Error: Something removed the coverage directory "/root/rea/coverage/.tmp"` - `ENOENT: no such file or directory, open '/root/rea/coverage/.tmp/coverage-1.json'` Config contributing context: - `vitest.config.ts` sets `coverage.enabled: true` and default reporter/paths. - No explicit `coverage.reportsDirectory` override. Impact: - CI noise after failures and potential instability when rerunning/retrying tests. Suggested fix: - Set a fixed stable coverage temp path per run/worker or disable shared temp cleanup during retries. - Option: add a per-run `coverage.reportsDirectory` under `tmpdir()` or configure retry-safe cleanup.
bsakaguchi 2026-10-15 18:21:06 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#98
No description provided.