You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have flaky failing tests due to unfound coverage files, but only on the CI (GitHub actions).
I previously created a bug ticket that was supposedly fixed, yet I'm still having the same issues.
⎯⎯⎯⎯⎯⎯ 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' }
Hello @C0ZEN. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.
Is it possible that Nx is running multiple vitest commands at the same time? Having more than one parallel Vitest runs could conflict in a way that other test run cleans up the coverage reports from previous run. You would need to make sure coverage.reportsDirectory is unique between the parallel test runs.
Describe the bug
I have flaky failing tests due to unfound coverage files, but only on the CI (GitHub actions).
I previously created a bug ticket that was supposedly fixed, yet I'm still having the same issues.
Note that I use Nx to run the tests.
Reproduction
Complicated to reproduce.
System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: