Investigate why code coverage badge in README shows such a low number

[yurishkuro]

Badge

Codecov

Pull request

Meanwhile, in the pull requests

[yurishkuro]

Possible explanation:

this points to a commit f313486 which is not even on the main branch, but a work in progress commit in another branch:

[Pushkarm029]

Yes, we see low code coverage due to a work-in-progress branch because there are a lot of indirect changes that significantly drops the codecov percentage.

Possible solution:

• instead of showing the main branch codecov, we show a release branch(eg: v1.52.0) coverage in the readme.
• & then write a GH Action to change the old release to the new release in the readme when a release comes.

->

[yurishkuro]

instead of showing the main branch codecov, we show a release branch

But why are changes from unrelated branch showing up in the badge if the badge is supposed to explicitly track the main branch? We do not merge random stuff into main, and we do not keep release branches, so the HEAD of main is the golden source, and its coverage is supposed to show as 95%.

[chirag-ghosh]

The badge now shows correct output:

Did anything change?

[Pushkarm029]

@chirag-ghosh, This is showing correctly now because the latest commit has 95% code coverage. It will break again if you make some significant code changes in an unrelated branch.

The primary purpose of this ticket is to investigate why codecov includes unrelated branch commits in the main. You can research more about it here.

[jkowall]

This seems to be resolved now, as the trends on https://app.codecov.io/gh/jaegertracing/jaeger look healthy.