Skip to content
coverage

feat: [P4PU-384] Porting from jest to vitest #364

Sign in to view logs

feat: [P4PU-384] Porting from jest to vitest

feat: [P4PU-384] Porting from jest to vitest #364

Triggered via pull request September 26, 2024 10:28
@mmoiommoio
synchronize #163
feat/P4PU-384-vitest
Status Failure
Total duration 1m 3s
Artifacts –

coverage_report.yml

on: pull_request
coverage
53s
coverage
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
coverage
Failed to parse the json-summary at path "/home/runner/work/arc-fe/arc-fe/coverage/coverage-summary.json." Make sure to run vitest before this action and to include the "json-summary" reporter. Original Error: Error: ENOENT: no such file or directory, open '/home/runner/work/arc-fe/arc-fe/coverage/coverage-summary.json' at async open (node:internal/fs/promises:636:25) at async readFile (node:internal/fs/promises:1246:14) at async ay (/home/runner/work/_actions/davelosert/vitest-coverage-report-action/v2/dist/index.js:70:800) at async uu (/home/runner/work/_actions/davelosert/vitest-coverage-report-action/v2/dist/index.js:70:881) at async Uq (/home/runner/work/_actions/davelosert/vitest-coverage-report-action/v2/dist/index.js:148:2032)
coverage
Error: ENOENT: no such file or directory, open '/home/runner/work/arc-fe/arc-fe/coverage/coverage-summary.json'
coverage
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
coverage
Unexpected input(s) 'package-manager', 'test-script', valid inputs are ['github-token', 'vite-config-path', 'json-summary-path', 'json-summary-compare-path', 'json-final-path', 'file-coverage-mode', 'working-directory', 'name', 'pr-number']