Description
After a CI build the lcov file is sent to codecov through the API, using the npm module codecov (v 3.5.0)
Once i reach the branch result on your webapp, there is a mix of different commits that doesn’t belong to the right branch.
the coverage graph is not available and everything seems mes sup
Repository
PM
Steps to Reproduce
- Hard to reproduce in steps but visible on my organization page.
Expected behavior: having the correct code coverage result
Actual behavior: having different coverage ( different branch )
Flakiness? [Does this happen all the time or only sometimes?]
Versions
Additional Information
Hi @buenjybar
(I’ve bumped your access so you can better post images and links)
Can you share an example commit that is showing on the wrong branch? Also, which branch did you upload it from, using the uploader?
I’m also experiencing this issue. In a commit on the master branch on our repository, we see:
==> Uploading reports
url: https://codecov.io
query: branch=master&commit=a41b03d111f65b531496b3b53231071cedaad8f6&build=508510&build_url=&name=&tag=&slug=scaleapi%2Fscaleapi&service=circleci&flags=&pr=&job=0
→ Pinging Codecov
https://codecov.io/upload/v4?package=bash-tbd&token=secret&branch=master&commit=a41b03d111f65b531496b3b53231071cedaad8f6&build=508510&build_url=&name=&tag=&slug=scaleapi%2Fscaleapi&service=circleci&flags=&pr=&job=0
→ Uploading
→ View reports at https://codecov.io/github/scaleapi/scaleapi/commit/a41b03d111f65b531496b3b53231071cedaad8f6
but when we go to the aforementioned report link, it’s tagged with a different branch name.