Codecov started showing 'There was an error processing coverage reports' since today, no changes on our side

Support Bug Fixes
1

Description

As can be seen from our project commits list, less than a day ago codecov started reporting errors. There have been no changes in codecov upload on our side. Build logs show no errors: reports are uploaded correctly.
For build we are using maven and jacoco, codecov is called from github actions.

Repository

CI/CD

Github actions

Uploader

codecov/codecov-action@v1

Commit SHAs

All recent commits. For example, 5354cb5150e4b890ba2439959b5897a719fed2c6

Codecov YAML

coverage:
  status:
    project:
      default:
        threshold: 2%

Codecov Output

==> Reading reports
    + ./diktat-common/target/site/jacoco/jacoco.xml bytes=22370
    + ./diktat-rules/target/site/jacoco/jacoco.xml bytes=446745
==> Appending adjustments
    https://docs.codecov.io/docs/fixing-reports
    + Found adjustments
==> Gzipping contents
==> Uploading reports
    url: https://codecov.io
    query: branch=dependabot%2Fmaven%2Forg.jacoco-jacoco-maven-plugin-0.8.6&commit=487060567379249cb6d54994ea0814e7235a1634&build=266801307&build_url=http%3A%2F%2Fgithub.com%2Fcqfn%2FdiKTat%2Factions%2Fruns%2F266801307&name=&tag=&slug=cqfn%2FdiKTat&service=github-actions&flags=unittests&pr=309&job=&cmd_args=f,n,F,Z
->  Pinging Codecov
https://codecov.io/upload/v4?package=bash-20200917-4e8f14b&token=secret&branch=dependabot%2Fmaven%2Forg.jacoco-jacoco-maven-plugin-0.8.6&commit=487060567379249cb6d54994ea0814e7235a1634&build=266801307&build_url=http%3A%2F%2Fgithub.com%2Fcqfn%2FdiKTat%2Factions%2Fruns%2F266801307&name=&tag=&slug=cqfn%2FdiKTat&service=github-actions&flags=unittests&pr=309&job=&cmd_args=f,n,F,Z
->  Uploading to
https://storage.googleapis.com/codecov/v4/raw/2020-09-22/C1474E822380CBE5BB59073F3F1A5339/487060567379249cb6d54994ea0814e7235a1634/5157f5d6-9b6a-46b4-aa9e-2993054be22c.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GOOG1EQX6OZVJGHKK3633AAFGLBUCOOATRACRQRQF6HMSMLYUP6EAD6XSWAAY%2F20200922%2FUS%2Fs3%2Faws4_request&X-Amz-Date=20200922T113227Z&X-Amz-Expires=10&X-Amz-SignedHeaders=host&X-Amz-Signature=9d38bd584301cc9446d2f82237432f23bcc6b1ab3716a9c64dc5c104b4518193
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 51098    0     0  100 51098      0  42369  0:00:01  0:00:01 --:--:-- 42369
100 51098    0     0  100 51098      0  41075  0:00:01  0:00:01 --:--:-- 41075
    -> View reports at https://codecov.io/github/cqfn/diKTat/commit/487060567379249cb6d54994ea0814e7235a1634

Steps to Reproduce

Currently any new commits to any branch are getting this behavior.

Expected behavior: Code coverage reports are correctly handled on codecov, data is reported to github.

Actual behavior: Codecov github check is stuck on waiting, codecov uploader doesn’t report any issues. On codecov.io message is ‘There was an error processing coverage reports’.

Flakiness? Happens all the time since at least commit ef18316e3d1567bcf8eea54193ea58abd89c5c76 (

Additional Information

Switching report expiration off doesn’t seem to change anything.

2

Hi @petertrr, I have started to see the same error since early morning.

I submitted another issue an hour ago. Let’s wait for an explanation from the support team.

3

@jpaya17, FYI, in our project the issue seems to be resolved now.
Edit: nope, it was working for some 40 minutes and then back to described behavior.

1 Like
4

Hi all, we’re taking a look to see what might have happened here, thanks for your patience.

1 Like
6

I have started to see the same error since yesterday too

7

We are seeing the exact the same issue but only on 1/3 of our repos. Codecov

9

same here. xxxxxxxxx

10

Hi @petertrr, @jpaya17, @JakeRoh, @michaelst, @adrian-hc we had an issue here. Would you be able to see if this is still happening?

11

since about 2 hrs ago i see all successful reports. lgtm!

1 Like
12

@tom It’s working fine again! Very much appreciated to the team! :slight_smile:

1 Like
13

@tom Yes, looks good now! Kudos to the team for a quick fix!

1 Like