Codecov fail_ci_if_error limits with --no-upload flag

Behavior of fail_ci_if_error with disabled uploads

The fail_ci_if_error flag is intended to ensure CI jobs fail when coverage data is missing or cannot be parsed. In local environments, using codecov --fail with a malformed coverage file typically triggers an immediate exit code 1. However, in CI environments, the uploader often operates as a background process, and documentation indicates that failure triggers are tied to the upload attempt.

There is an unresolved ambiguity regarding the interaction between fail_ci_if_error and the --no-upload flag. It is unclear if a parsing error is sufficient to trigger a non-zero exit code when the actual upload process is suppressed.

Specific questions:

• Does fail_ci_if_error cause a CI job to fail when --no-upload is active and a parse error occurs?
• What is the expected exit status for a malformed coverage file when uploads are disabled?
• Is there a documented configuration to enforce CI failure on parse errors independently of the upload status?