Coverage report processing error - help!


I’ve been trying to get my code coverage reports processed by with no luck. GitHub Actions is sending the report and the web request gets a successful response. However, when I go to see the report on the Codecov dashboard, I get the message that there was an error processing the report. Unfortunately, no additional information is provided in the dashboard. At this point, I’m stuck, so any help would be very much appreciated.

Commit SHAs



CI/CD or Build URL


GitHub Actions

Codecov Output

_____ _

[27]( / ____| | |

[28]( | | ___ __| | ___ ___ _____ __

[29]( | | / _ \ / _` |/ _ \/ __/ _ \ \ / /

[30]( | |___| (_) | (_| | __/ (_| (_) \ V /

[31]( \_____\___/ \__,_|\___|\___\___/ \_/


[33]( Codecov report uploader 0.1.0

[34]([2021-09-18T00:06:41.655Z] ['info'] => Project root located at: /home/runner/work/openfast/openfast

[35]([2021-09-18T00:06:41.656Z] ['info'] -> No token specified or token is empty

[36]([2021-09-18T00:06:41.656Z] ['verbose'] Start of network processing...

[37]([2021-09-18T00:06:41.656Z] ['verbose'] Searching for files in /home/runner/work/openfast/openfast

[38]([2021-09-18T00:06:41.759Z] ['info'] Searching for coverage files...

[39]([2021-09-18T00:06:41.855Z] ['info'] => Found 1 possible coverage files:

[40]( ./regressioncov.txt

[41]([2021-09-18T00:06:41.856Z] ['verbose'] End of network processing

[42]([2021-09-18T00:06:41.856Z] ['info'] Processing ./regressioncov.txt...

[43]([2021-09-18T00:06:41.897Z] ['info'] Detected GitHub Actions as the CI provider.

[44]([2021-09-18T00:06:41.897Z] ['verbose'] -> Using the following env variables:

[45]([2021-09-18T00:06:41.897Z] ['verbose'] GITHUB_ACTION: __codecov_codecov-action

[46]([2021-09-18T00:06:41.897Z] ['verbose'] GITHUB_HEAD_REF:

[47]([2021-09-18T00:06:41.897Z] ['verbose'] GITHUB_REF: refs/heads/cc

[48]([2021-09-18T00:06:41.897Z] ['verbose'] GITHUB_REPOSITORY: rafmudaf/openfast

[49]([2021-09-18T00:06:41.897Z] ['verbose'] GITHUB_RUN_ID: 1247357038

[50]([2021-09-18T00:06:41.897Z] ['verbose'] GITHUB_SERVER_URL: [](

[51]([2021-09-18T00:06:41.897Z] ['verbose'] GITHUB_SHA: ec100ca093667284e8b4fe38e2d731b88f5a4d57

[52]([2021-09-18T00:06:41.897Z] ['verbose'] GITHUB_WORKFLOW: Development Pipeline

[53]([2021-09-18T00:06:41.898Z] ['info'] Pinging Codecov:*******&branch=cc&build=1247357038&

[54]([2021-09-18T00:06:41.898Z] ['verbose'] Passed token was 0 characters long

[55]([2021-09-18T00:06:41.898Z] ['verbose']

[56]( Content-Type: 'text/plain'

[57]( Content-Encoding: 'gzip'

[58]( X-Reduced-Redundancy: 'false'

[59]([2021-09-18T00:06:42.297Z] ['verbose'] Returned upload url:


[61]([2021-09-18T00:06:42.297Z] ['verbose']

[62]( Content-Type: 'text/plain'

[63]( Content-Encoding: 'gzip'

[64]([2021-09-18T00:06:42.297Z] ['info'] Uploading...

[65]([2021-09-18T00:06:42.550Z] ['info'] {"status":"success","resultURL":""}

Expected Results

I expected that the coverage report would be processed by the Codecov system.

Actual Results

Instead, I get the message that there is an error processing my reports.

@rafmudaf it looks like the file format is not one that we accept. What are you using to generate coverage reports?

I would guess if they have an XML or json file format, that that would be accepted.

Hi @tom Thanks for pointing that out. What part of the error message pointed you to that? I’d really like to understand how to debug these problems better.

Also @tom I used gcov and gcovr to produce initially an html coverage report. Then I saw in your docs that html is not supported so I tried a text based coverage report. I’ll try XML now.

@tom the Cobertura XML format from gcovr did work! Good catch.

In any case, I’d still like to understand where you got the feedback that the file format was not supported. I made the assumption that the text format from gcovr was included in this line in the docs:

Most of .txt format types (Lcov TXT, Gcov TXT, Golang Txt)

Clearly, that was a bad assumption, but it took quite a bit of time to get to this point. It would be great to understand how to debug these things going forward.

@rafmudaf I don’t have a better answer than I had a hunch after looking at your setup and coverage report filename. I have mentioned to the product team about your issue specifically and maybe working on more specific error messaging.

That said, is everything working for you now?

Hey @tom

Yes things are working well, at the moment.

If I can make a suggestion to the product team, it would be very helpful to see some logs. Even a successful status code doesn’t necessarily mean things are working the way the user intends. The ability to see the commands being run and how the computer is responding is critical in debugging. Otherwise, we’re left just guessing and poking at the system in different ways to see how it responds. An example of good logs are the GitHub Actions logs. They give you a ton of information and that makes recreating issues super easy.

If storage is a concern for Codecov, consider that the GitHub Actions logs expire after something like 30 days, so it’s not a user expectation to have logs available for a long time. Even 5 days would be enough to bridge a weekend.


1 Like

@rafmudaf oh I totally understand. I know that right now it’s super opaque and not a great experience when debugging. Right now everything runs asynchronously, so it’s not obvious when something happens (and to log it back to the Action). We are looking into making more logs after upload (and during processing) onto the product side.