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
Describe the bug
In between runs of the CLI, there is a fs error from attempting to open coverage-ts/typescript-coverage.json - seems in clearing the dir for the new report, it also attempts to open it.
[Error: ENOENT: no such file or directory, open 'coverage-ts/typescript-coverage.json'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: 'coverage-ts/typescript-coverage.json'
}
To Reproduce
Run the CLI from a clean install, below is my config:
Noticed that the issue seems to have arisen from mistakenly including " coverage-ts/assets/source-file.js" in the report, after adding that to the ignoreFiles I can consistently run the reports, not sure why this would present the error that occurs though
Describe the bug
In between runs of the CLI, there is a
fs
error from attempting to opencoverage-ts/typescript-coverage.json
- seems in clearing the dir for the new report, it also attempts to open it.To Reproduce
Run the CLI from a clean install, below is my config:
Observe that
coverage-ts/typescript-coverage.json
is produced, re-run the CLI and it is deleted but the CLI exits with error code 255Expected behaviour
Exits with error code 0
Assets to be produced
Screenshots
CLI output from 3 consecutive runs with no other changes:
FS after a SUCCESSFUL run:
FS after a FAILED run Note: assets aren't generated nor the json coverage
Environment
The text was updated successfully, but these errors were encountered: