No such file or directory for coverage files

[C0ZEN]

Describe the bug

After the migration to Vite 5, I started having flaky failing tests due to unfound coverage files, but only on the CI (GitHub actions).

Error:  
⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯
Error:  Error: ENOENT: no such file or directory, open '/home/runner/actions-runner/_work/x/.tmp/coverage-9.json'
Error:  ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Error:  Serialized Error: { errno: -2, code: 'ENOENT', syscall: 'open', path: '/home/runner/actions-runner/_work/x/.tmp/coverage-9.json' }
Error:  

Note that I use Nx to run the tests.

Reproduction

N/A

System Info

GitHub Actions
Vitest 1
Vite 5

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[github-actions]

Hello @C0ZEN. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[AriPerkkio]

I can reproduce this on watch mode. If test re-run is triggered while current run is looping through coverage results, the next run will remove the files and earlier run will cause this error.

In browser mode this is easily reproducible by opening Vitest UI in multiple tabs.

[AriPerkkio]

After testing multiple different solutions for this, I think the best option is to make coverage providers aware of earlier runs. They should keep similar runningPromise reference as Vitest's core.ts does. In CoverageProvider.clean() we would check if runningPromise is still defined, await it if it is, and only after that allow clean() to continue. In CoverageProvider.reportCoverage() the runningPromise would be resolved at the end. After some testing this solution seems to work the best.

In clean() there could even be a warning logged if runningPromise is defined. Something like 'Warning: Trying to start new coverage collection before earlier run ended. Waiting for earlier run to finish before starting.'.

I've also tried to implement some kind of cancelling mechanism to abort earlier runs. Not sure if that's needed.