Codecov processing failure with no error message

Support
1

A few weeks ago, codecov stopped working for my personal project located at GitHub - grumpycoders/pcsx-redux: Latest iteration of PCSX, the popular open source PlayStation 1 emulator, heavily focused on development, debuggability, and reverse engineering, but still perfectly usable to run PlayStation 1 titles. in a weird way, with little to no change in the repository itself.

The code coverage job configuration can be seen here:
https://github.com/grumpycoders/pcsx-redux/blob/main/.circleci/config.yml#L50-L88

What happens is the circleci job completes successfully, and successfully sends the coverage report to codecov with no problem whatsoever:

https://app.circleci.com/pipelines/github/grumpycoders/pcsx-redux/2319/workflows/8e4a8733-cda9-4c3d-b47c-f4c2cdc35da8/jobs/4066

The ā€œUpload Code Coverageā€ section says the following at the end:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3838k    0     0  100 3838k      0  9547k --:--:-- --:--:-- --:--:-- 9547k
    -> Reports have been successfully queued for processing at https://codecov.io/github/grumpycoders/pcsx-redux/commit/b025a8d7fc6214ee23c9a06afcb5602ce9f181c4
CircleCI received exit code 0

But on the codecov website, I see this:

ā€œThere was an error processing coverage reports.ā€ and no error message whatsoever to indicate what went wrong exactly, which isnā€™t helpful in troubleshooting whatā€™s going on.

Anyone has an idea on where to begin troubleshooting whatā€™s going on?

2

@nicolasnoble can you check that the file you are uploading has coverage information? You can do do cat ./coverage.txt (based off of this CI run)

3

Yes, the file exists, and seems proper. Here you have a copy of it, that I grabbed using circleciā€™s ssh shell debugging:

https://static.grumpycoder.net/pixel/coverage.txt

The job I just ran to get this file using circleci is at https://app.circleci.com/pipelines/github/grumpycoders/pcsx-redux/2331/workflows/a8df69bd-755c-4f29-a441-37a595f394ea/jobs/4093 and the job says it uploaded successfully at Code coverage done right. which still contains the same blank error.

4

My reply seems stuck in spam limbo, probably because Iā€™ve posted the several megabytes coverage.txt file Iā€™ve extracted from the job.

5

@nicolasnoble fair enough. Iā€™m not too familiar with lcov, but Iā€™m guessing it has to do with the file format that we are receiving. Iā€™ll see if I can get some help from our product team here.

6

I mean it used to work before, and it stopped working all of a sudden with no reason nor warning.

7

Alright well, after changing the exporter to lcov, this is now working again:

I guess the previous format (that seems to be the documented method still?) isnā€™t working properly anymore, which may still be something relevant for people to know.

1 Like