codecov/codecov-action failed to properly upload report on v4
codecov/codecov-action failed to properly upload report is the third of three near-identical sentences the v4 action can print, and the one it prints tells you how far the run got before something broke. The sentence carries no diagnosis of its own: what follows the colon is an @actions /exec message naming a binary and an exit code, and the reason that binary exited lives in the lines above it.…
The failure message "Codecov: Failed to properly upload report" indicates that the Codecov action encountered an issue while attempting to upload the coverage report during the v4 action. This sentence is one of three identical messages that the v4 action can print, each describing the point at which the run encountered a problem.
Unlike the other two sentences, this one does not provide a diagnosis on its own; instead, it provides information about where the failure occurred in the process. The message consists of an @actions/exec message that includes a binary name and an exit code, and the reason for the binary's failure is contained in the lines above it.
The three failure messages in the v4 action come from the source code located in src/index.ts at version 4. The error message suggests that the coverage step reported a failure to upload the report but typically does not turn the job red. The failure is identified by the stage name used in the sentence, which can be "create commit," "create report," or "upload report."
The action executes these three sub-commands of the Codecov binary in this order, and the failure indicates that the previously executed stage has succeeded. The failure message also includes a prefix that provides additional context about the nature of the error. If the prefix is "Warning," it means that the failure was routed through core.warning, and the step remained green.
If the prefix is "Error," it means that core.setFailed ran, and the process was ended. The action's failure message is specific to version 4 and does not apply to previous versions or future versions of the action. It provides a detailed breakdown of the failure, including the binary that failed, the exit code, and the reason for the failure, which is usually a rejected token, a report that the service refused, or a transfer that did not complete.
To fix the issue, it is necessary to identify the sub-command line and read upward to find the cause of the failure. Once the cause is identified, the appropriate action can be taken, such as explicitly setting `fail_ci_if_error` to true or false, depending on the desired behavior. The failure message also highlights the importance of matching the guidance to the version of the action being used to avoid confusion and ensure that the correct troubleshooting steps are followed.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
