This repository was archived by the owner on Jul 23, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 65
Mono repository incorrectly reporting success #169
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededneed-more-infoNeed additional information to debug/reproduceNeed additional information to debug/reproduce
Description
Is your feature request related to a problem? Please describe.
When running the following GitHub Action on a Lerna mono-repository if any single package fails, it still reports success.
In my example, the projectRoot incorrectly pointed to ../../../
instead of below code block, causing format_coverage to break, yet GH Action codeclimate-action to report success though really fail.
"coverageReporters": [
"json",
[
"lcov", {"projectRoot": "../../"}
]
],
Describe the solution you'd like
Accurately report status as success and see that through on the Code Climate settings test reporting pages.
Additional context
Add any other context or screenshots about the feature request here.
Actual Error
Error: open workspace/sites/fast-component-explorer/app/app.tsx: no such file or directory
| Usage:
| cc-test-reporter format-coverage [coverage file] [flags]
|
| Flags:
| --add-prefix string add this prefix to file paths
| -t, --input-type string type of input source to use [clover, cobertura, coverage.py, excoveralls, gcov, gocov, jacoco, lcov, simplecov, xccov]
| -o, --output string output path (default "coverage/codeclimate.json")
| -p, --prefix string the root directory where the coverage analysis was performed (default "/github/workspace")
|
| Global Flags:
| -d, --debug run in debug mode
|
| (node:5413) UnhandledPromiseRejectionWarning: TypeError: (s || "").replace is not a function
| at escapeData (/actions/[email protected]/node_modules/@actions/core/lib/command.js:66:10)
| at Command.toString (/actions/[email protected]/node_modules/@actions/core/lib/command.js:60:35)
| at issueCommand (/actions/[email protected]/node_modules/@actions/core/lib/command.js:23:30)
| at Object.issue (/actions/[email protected]/node_modules/@actions/core/lib/command.js:27:5)
| at Object.error (/actions/[email protected]/node_modules/@actions/core/lib/core.js:127:15)
| at /actions/[email protected]/lib/main.js:135:28
| at Generator.throw (<anonymous>)
| at rejected (/actions/[email protected]/lib/main.js:6:65)
| at processTicksAndRejections (internal/process/task_queues.js:97:5)
| (node:5413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
| (node:5413) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[CI - FAST Local Testing/build_local_linux] ✅ Success - Collect and upload code coverage to Code Climate
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededneed-more-infoNeed additional information to debug/reproduceNeed additional information to debug/reproduce