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
Been seeing this error when running tests in GitHub Actions CI for a bit now:
Failed to write coverage reports:
ERROR: Error: ENOENT: no such file or directory, open '/home/runner/work/rdme/rdme/coverage/coverage-final.json'
STACK: Error: ENOENT: no such file or directory, open '/home/runner/work/rdme/rdme/coverage/coverage-final.json'
at Object.openSync (fs.js:498:3)
at FileWriter.writeFile (/home/runner/work/rdme/rdme/node_modules/istanbul-lib-report/lib/file-writer.js:185:41)
at JsonReport.onStart (/home/runner/work/rdme/rdme/node_modules/istanbul-reports/lib/json/index.js:17:45)
at Visitor.value (/home/runner/work/rdme/rdme/node_modules/istanbul-lib-report/lib/tree.js:38:38)
at ReportTree.visit (/home/runner/work/rdme/rdme/node_modules/istanbul-lib-report/lib/tree.js:126:17)
at JsonReport.execute (/home/runner/work/rdme/rdme/node_modules/istanbul-lib-report/lib/report-base.js:12:44)
at /home/runner/work/rdme/rdme/node_modules/@jest/reporters/build/CoverageReporter.js:241:12
at Array.forEach (<anonymous>)
at CoverageReporter.onRunComplete (/home/runner/work/rdme/rdme/node_modules/@jest/reporters/build/CoverageReporter.js:229:25)
at ReporterDispatcher.onRunComplete (/home/runner/work/rdme/rdme/node_modules/@jest/core/build/ReporterDispatcher.js:71:9)
Not sure why, but jest coverage started breaking somewhere between this commit and this commit.
I messed around in #701 and I think the double /rdme/rdme thing is expected? I tried a few values for coverageDirectory and that didn't appear to work either 😞
Been seeing this error when running tests in GitHub Actions CI for a bit now:
Not sure why, but jest coverage started breaking somewhere between this commit and this commit.
Anything weird jumping out here? 🧐 ca998bc...65a209a
See #701 #611 #610 for various attempts to address this.
The text was updated successfully, but these errors were encountered: