# "There is an error processing the coverage reports "

**URL:** <https://community.codecov.com/t/there-is-an-error-processing-the-coverage-reports/3866>\
**Category:** Support\
**Created:** [September 16, 2022, 2:09pm UTC](https://community.codecov.com/t/there-is-an-error-processing-the-coverage-reports/3866 "2022-09-16T14:09:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![h-2](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/h-2/32/2643_2.png) [@h-2](https://community.codecov.com/u/h-2)\
**Post date:** [September 16, 2022, 2:09pm UTC](https://community.codecov.com/t/there-is-an-error-processing-the-coverage-reports/3866/1 "2022-09-16T14:09:31Z")

</div>

## 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](https://github.com/apps/codecov), if using GitHub  
 I have [validated](https://docs.codecov.com/docs/codecov-yaml#validate-your-repository-yaml) my `codecov.yaml` configuration file.  
 I have filled out the below sections to the best of my ability.

### Description

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

### CI/CD URL

It can be seen here:

> **[Code coverage done right.](https://app.codecov.io/gh/biocpp/biocpp-core/pulls)**
>
> Hosted coverage report highly integrated with GitHub, Bitbucket and GitLab. Awesome pull request comments to enhance your QA.

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

This is an example CI-run:  
[https://github.com/biocpp/biocpp-core/actions/runs/2720020243/jobs/4256709686](https://github.com/biocpp/biocpp-core/actions/runs/2720020243/jobs/4256709686)

### Codecov Output

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

```auto
Run codecov/codecov-action@v2
==> linux OS detected
https://uploader.codecov.io/latest/linux/codecov.SHA256SUM
==> 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:
  /home/runner/work/biocpp-core/biocpp-core/biocpp-core-build/biocpp_coverage.xml
[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
https://storage.googleapis.com/codecov/v4/raw/2022-07-22/D7C3555C55AB87E0B0B686E30FC7B73B/8160ec6afc961e1c0a709a617db0841b28da6002/d12122ca-c778-47cf-ad4f-f403f8031ad3.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GOOG1EJOGFN2JQ4OCTGA2MU5AEIT7OT5Z7HTFOAN2SPG4NWSN2UJYOY5U6LZQ%2F20220722%2FUS%2Fs3%2Faws4_request&X-Amz-Date=20220722T170102Z&X-Amz-Expires=10&X-Amz-SignedHeaders=host&X-Amz-Signature=3f27e7d876bbc7a84a4fdeaaf19e737ad0cfb38cb766c29ac86aac0dc8709191
[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

–

---

<div class="post-metadata">

**Author:** ![h-2](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/h-2/32/2643_2.png) [@h-2](https://community.codecov.com/u/h-2)\
**Post date:** [September 16, 2022, 2:29pm UTC](https://community.codecov.com/t/there-is-an-error-processing-the-coverage-reports/3866/2 "2022-09-16T14:29:07Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ferdnyc](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/ferdnyc/32/1627_2.png) [@ferdnyc](https://community.codecov.com/u/ferdnyc)\
**Post date:** [September 17, 2022, 5:27pm UTC](https://community.codecov.com/t/there-is-an-error-processing-the-coverage-reports/3866/3 "2022-09-17T17:27:55Z")

</div>

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:

```nohighlight
  -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.
