Missing base report

👍

Improving this feature. Please share feedback on our customer feedback dashboard.

https://github.com/codecov/feedback/

In order to produce an accurate coverage comparison, Codecov must have the coverage report for the pull request base.

Best Practice: Always fork a branch from a successful CI commit that has coverage uploaded, as illustrated below.

This issue occurs when the base commit (the parent commit of the first commit on the pull request) did not upload coverage and/or failed CI tests.

# [legend] P=CI-Passed, F=CI-Failed, .=No-CI-Ran# Illustration Amaster . F . .pull      \ . . P# Base commit's CI failed therefore base report is invalid.# Resulting in "missing base report"------------------------------------------------# Illustration Bmaster . . . .pull        \ . . P# Base commit has no reports uploaded.# Resulting in "missing base report"------------------------------------------------# Illustration Cmaster Ppull    \ . . P# Base and head commits passed CI and uploaded coverage to Codecov.# Resulting in a beautiful comment being posted.

Next: Read aboutComparing Commits.

Missing head commit

You will see an error stating No coverage uploaded for pull request head. when the pull request has:

• not yet uploaded coverage results to Codecov;
• or the uploaded reports are from failed CI builds.

Unknown Author

If your commit is showing author as"Unknown", here is how to fix it.

Your git provider (i.e. GitHub) is not returning the author id in the commit api result. This is because the email used to commit is not the same as your Github account.

Edit the user email found in your~/.gitconfig:

[user]name = Your Nameemail =[email protected]  # make sure the email is the same you login to Github

No statuses or pull requests are posting

This issue is likely caused by the bot losing authentication to your project. Learn moreTeam Bot.

Unusable Reports

"Unusable report" can happen for a few reasons:

1. The uploader wasn't able to find your source code. Normally the uploader will scan the git tree to assemble a list of files in your repo or check the directory If there isn't a.git directory found. This is because Codecov needs to find which file in your repo the report is referring to. If we find more than 1 match or no match, we cannot fully process coverage and discard the report to avoid inaccurate info.
2. Paths don't match. So Codecov can't map the coverage data back to files in the repo seeOur path fixing page to resolve.
3. The report is actually empty - nothing was uploaded, so we just received the network and no coverage data.
   To check if your uploaded report is empty (containing no coverage data) please download the reports by
   clickingDownload in the build logs. Look for the file by searching the string# path=. Review each file to
   confirm if coverage was properly collected.
4. The report isn't coverage data. This may also trigger 'processing failed' though, but when Codecov receives something it cannot identify as coverage, it will indicate an error.

400 Errors when uploading coverage

If you're usingcodecov-python,codecov-node, orcodecov-exe to upload coverage, please try ouruniversal binary uploader.

📘

Additional FAQ

There are additional frequently asked questionslinked here.

Updated over 1 year ago