question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Codecov reports upload but does not process report

See original GitHub issue

This is my .codecov.yml file

codecov:
  notify:
    require_ci_to_pass: yes

coverage:
  precision: 2
  round: down
  range: "85...100"

  status:
    project: yes
    patch: yes
    changes: no

parsers:
  gcov:
    branch_detection:
      conditional: yes
      loop: yes
      method: no
      macro: no

comment:
  layout: "header, diff"
  behavior: default
  require_changes: no

fixes:
  - "/home/travis/build/::"

Here is the log

$ nyc report --reporter=text-lcov > coverage.lcov && codecov
  _____          _  
 / ____|        | |  
| |     ___   __| | ___  ___ _____   __  
| |    / _ \ / _` |/ _ \/ __/ _ \ \ / /  
| |___| (_) | (_| |  __/ (_| (_) \ V /  
 \_____\___/ \__,_|\___|\___\___/ \_/  
                                v3.1.0
==> Detecting CI Provider
    Travis CI Detected
==> Configuration: 
    Endpoint: https://codecov.io
{ commit: '3efd2321db4376e49f30653174c8c828dad03f05',
  branch: 'thomas/codecov-setup',
  package: 'node-v3.1.0' }
==> Building file structure
==> Generating gcov reports (skip via --disable=gcov)
    $ find /home/travis/build/benmacdonald/capstone -type f -name '*.gcno'  -exec gcov  {} +
==> Scanning for reports
    + /home/travis/build/benmacdonald/capstone/backend/api/coverage.lcov
==> Uploading reports
    Success!
    View report at: https://codecov.io/github/benmacdonald/capstone/commit/3efd2321db4376e49f30653174c8c828dad03f05

From this I the failed to process reports.

Anyone can point me in the right direction or have the solution?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:16
  • Comments:13 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
rolznzcommented, Sep 26, 2019

Tried for hours and then switched to coveralls… instant success.

2reactions
drazisilcommented, Sep 27, 2019

@styfle that’s correct. Since we need to match the files in the report to files in the repo, you have to run the coverage against the typescript files as the dist files aren’t in the commit for us to see.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Coverage Reports uploaded, CI Passed, but Codecov site ...
As far as I can tell, it isn't still “being processed,” and there has been a “coverage report uploaded” so this must mean...
Read more >
Commits showing "Reports Not Uploaded"
If commits are showing as "No report uploaded yet", there are two common causes for this: Normally, the Codecov uploader will not ......
Read more >
Features - Codecov
Report Merging. Do you generate multiple coverage reports? Codecov can handle merging them seamlessly, whether you upload multiple reports at once or across ......
Read more >
Coverage reports not being processed by codecov anymore
In codecov I can see where the upload attempts to process, but it fails without much description: There was an error processing coverage...
Read more >
Code coverage - Scikit-HEP
Configuring Codecov and uploading coverage reports. Interestingly, Codecov does not require any initial configurations for your project, given that you have ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found