Report has been processing for more than 24 hours. Is that normal?


I have uploaded this report more than 24 hours ago and it’s still waiting in a queue. Is that normal.


Hi @PauliusLiekis, can you provide a copy of your Codecov output? I’m seeing that we never received the actual coverage report.


We’ve been having problems with codecov for past week (maybe more). There are no errors in CircleCI, but usually if I go to codecov page it says “There was an error processing coverage reports.” (

The original report from my first post is still says this: “Reports are queued for processing… Please review report with caution, it may change.”. I submitted this from my own computer.

It used to work fine, but it got broken for both repositories that we have integration for.

Hi @PauliusLiekis, this is pretty strange. I’m seeing in our logs that we received a request to upload, but no actual file. Is this still happening for you, and if so, can you supply the Codecov output?

I executed it again:

> fatmap@ coverage:upload /Users/paulius/Fatmap/Web/fatmap.js2
> codecov -f coverage/coverage-final.json -t <REDACTED>

  _____          _  
 / ____|        | |  
| |     ___   __| | ___  ___ _____   __  
| |    / _ \ / _` |/ _ \/ __/ _ \ \ / /  
| |___| (_) | (_| |  __/ (_| (_) \ V /  
 \_____\___/ \__,_|\___|\___\___/ \_/  
==> Detecting CI Provider
    No CI Detected. Using git/mercurial
==> Configuration: 
{ commit: '67eec59fcbb3c98ab9ba169eccd384ec288193f3',
  branch: 'task/LP-403--smoothed-gpx-export',
  package: 'node-v3.5.0' }
==> Building file structure
==> Generating gcov reports (skip via --disable=gcov)
    $ find /Users/paulius/Fatmap/Web/fatmap.js2 -type f -name '*.gcno'  -exec gcov  {} +
==> Targeting specific file
    + /Users/paulius/Fatmap/Web/fatmap.js2/coverage/coverage-final.json
==> Uploading reports
    View report at:

The uploaded file:

Hi @PauliusLiekis, could you try again after upgrading your codecov package to latest?

Yes, I confirm that updating to latest fixed our problem.

We had one project on 3.5.0 and other on 3.6.5. I upgraded them both to 3.7.0 - that fixed our problems.


1 Like