Unable to find commits in bit-bucket, though upload was successful

#1

Description

report is in processing always
image
though upload was successful

 / ____|        | |  
| |     ___   __| | ___  ___ _____   __  
| |    / _ \ / _` |/ _ \/ __/ _ \ \ / /  
| |___| (_) | (_| |  __/ (_| (_) \ V /  
 \_____\___/ \__,_|\___|\___\___/ \_/  
                                v3.6.1
==> Detecting CI Provider
    No CI Detected. Using git/mercurial
==> Configuration: 
    Endpoint: https://codecov.io
{
  commit: '120142bc3285d0dca2dbd170d6d44e51b2c0f375',
  branch: 'master',
  package: 'node-v3.6.1'
}
==> Building file structure
==> Generating gcov reports (skip via --disable=gcov)
    $ find /home/john/dev/rokt-bff -type f -name '*.gcno'  -exec gcov  {} +
==> Scanning for reports
    + /home/john/dev/rokt-bff/coverage/clover.xml
    + /home/john/dev/rokt-bff/coverage/lcov.info
==> Uploading reports
    Success!
    View report at: https://codecov.io/bitbucket/ROKT/op2-bff/commit/120142bc3285d0dca2dbd170d6d44e51b2c0f375

have i missed anything?

Repository

https://codecov.io/bb/ROKT/op2-bff

Versions

OS: Ubuntu,
Language: node,
Codecov version: codecov-node

Additional Information

codecov yaml settings:

coverage:
  range: 70..100
  round: down
  precision: 2
fixes:
  - "/home/john/dev/rokt-bff/::"
#3

I’m having the same issue. Could this possibly be related to: OPEN ISSUE INVESTIGATION: Report stuck in processing + Unable to find report content in storage archive ?

#4

Ok it seems that they have fixed that issue, but I am still experiencing this one. Does anyone have an idea about why this happens?

#5

It’s usually path matching https://docs.codecov.io/docs/fixing-paths or an actually empty report. In some cases it’s an expired report. https://docs.codecov.io/docs/codecov-yaml#section-expired-reports.

It could also be credentials, if BitBucket tells us the commit doesn’t exists we can’t do much more.

I would need a commit SHA to dig deeper.