You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the only way for Codecov to compare against is by the coverage reported from a commits’ parents. If those don’t exist, Codecov will keep going backwards until it hits a commit that has coverage.
I looked into the actions for this repo and noticed that the last run for main uploaded the codecov results for @tigrannajaryan's branch and not this repo even though it was run against main of this repo.
This was first mentioned by @srikanthccv in a comment on #192 and I noticed the issue on my recent PR as well #209.
When looking at the codecov report for #209, it indicates that it is comparing to a BASE that is 29 commits old.
@srikanthccv submitted this issue to codecov codecov/feedback#123
I tried to dig into this a little more and am creating this issue to add some things I discovered.
I noticed a similar issue in the community boards which mentions how codecov finds the base branch. https://community.codecov.com/t/how-to-prevent-codecov-from-using-a-commit-older-than-the-base-of-the-pr-to-do-comparison/3513
I looked into the actions for this repo and noticed that the last run for main uploaded the codecov results for @tigrannajaryan's branch and not this repo even though it was run against main of this repo.
Actions job for most recent merge to main: https://github.com/open-telemetry/opamp-go/actions/runs/6551245736
test-coverage log output:
I suspect this is the source of the problem, but I don't know how to fix it.
The text was updated successfully, but these errors were encountered: