"There is an error processing the coverage reports "

Before submitting a topic, please confirm the following

I have searched for similar issues before creating this topic.
I have verified that my repository is using the Codecov GitHub app, if using GitHub
I have validated my codecov.yaml configuration file.
I have filled out the below sections to the best of my ability.


Everything was working fine until a few commits ago. Now the Coverage-CI still passes, but I don’t get reports, any more.


It can be seen here:

Until pr#31 everything is fine; then it stops working.

This is an example CI-run:

Codecov Output

Please provide the full output of running the uploader on your CI/CD. This will typically have the Codecov logo as ASCII.

Run codecov/codecov-action@v2
==> linux OS detected
==> SHASUM file signed by key id 806bb28aed779869
==> Uploader SHASUM verified (432553f03714a83ab5cac78be2e7fe6a6050767f78f77e9c7a84bdb1c34a0bd3  codecov)
==> Running version latest
==> Running version v0.2.4
/home/runner/work/_actions/codecov/codecov-action/v2/dist/codecov -n  -Q github-action-2.1.0 -f /home/runner/work/biocpp-core/biocpp-core/biocpp-core-build/biocpp_coverage.xml -C 8160ec6afc961e1c0a709a617db0841b28da6002 -R /home/runner/work/biocpp-core/biocpp-core/biocpp-core
[2022-07-22T17:01:02.055Z] ['info'] 
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/

  Codecov report uploader 0.2.4
[2022-07-22T17:01:02.056Z] ['info'] => Project root located at: /home/runner/work/biocpp-core/biocpp-core/biocpp-core
[2022-07-22T17:01:02.059Z] ['info'] -> No token specified or token is empty
[2022-07-22T17:01:02.068Z] ['info'] Searching for coverage files...
[2022-07-22T17:01:02.132Z] ['info'] => Found 1 possible coverage files:
[2022-07-22T17:01:02.132Z] ['info'] Processing /home/runner/work/biocpp-core/biocpp-core/biocpp-core-build/biocpp_coverage.xml...
[2022-07-22T17:01:02.138Z] ['info'] Detected GitHub Actions as the CI provider.
[2022-07-22T17:01:02.140Z] ['info'] Pinging Codecov: https://codecov.io/upload/v4?package=github-action-2.1.0-uploader-0.2.4&token=*******&branch=fork&build=2720020243&build_url=https%3A%2F%2Fgithub.com%2Fbiocpp%2Fbiocpp-core%2Factions%2Fruns%2F2720020243&commit=8160ec6afc961e1c0a709a617db0841b28da6002&job=Linux+CI&pr=31&service=github-actions&slug=biocpp%2Fbiocpp-core&name=&tag=&flags=&parent=
[2022-07-22T17:01:02.849Z] ['info'] https://codecov.io/github/biocpp/biocpp-core/commit/8160ec6afc961e1c0a709a617db0841b28da6002
[2022-07-22T17:01:02.850Z] ['info'] Uploading...
[2022-07-22T17:01:03.082Z] ['info'] {"status":"success","resultURL":"https://codecov.io/github/biocpp/biocpp-core/commit/8160ec6afc961e1c0a709a617db0841b28da6002"}

Expected Results

  • I expect to get results and a comment on my Github.
  • (unrelated) I expect the CI run to fail if it can’t upload the results. Apparently it thinks that submitting was successful.

Actual Results

Codecov no longer has results. CI still seems to pass.

Additional Information

The error was in changed paths that led to the coverage looking in the wrong folder. I still would have expected some kind of error.

1 Like

Mmm, yeah… the problem is, the coverage file was still generated by gcovr — it was just (presumably) basically empty. Hard to say that Codecov should flag that as an error, there certainly could be plenty of valid situations where certain CI runs produce no coverage data, like in an aggregate situation where they’ll be combined with others that do show results. You wouldn’t want those uploads erroring out on people just because they happen to contain no results.

gcovr has a -s flag that tells it to summarize results to the terminal:

  -s, --print-summary   Print a small report to stdout with line & branch
                        percentage coverage. This is in addition to other
                        reports. Default: False.

Adding that to your gcovr command line might at least make it more obvious when the coverage data isn’t being generated properly, from looking at the CI logs.

1 Like