-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Describe the bug
Opening on behalf of a customer:
One of our engineers noticed some differences in coverage numbers between the Flags page and the Overview page with the flag selected. In the attached screenshot, the Flags page shows that there is
41.44%coverage for the flagmy-flag. If I click on the flag name from that page, I'm brought to the overview page with themy-flagflag selected and a filtered set of directories. However, the tree view on the page shows49.19%coverage. I went to our continuous integration pipeline and downloaded thecoverage.outfile that is being sent to Codecov. When I ran the following command on it:
$ go tool cover -func=coverage.out
I see that the total statement coverage is 49.9%, which roughly aligns with what we're seeing in the Codecov Overview page but not the Flags page. Could you let me know if there is a reason for the different numbers?
To Reproduce
Steps to reproduce the behavior:
(internal customer case contains link to customer instance, real flag name, and coverage.out file)
- Go to Overview page
- Select the
my-flagflag, see 49.19% coverage - Visit the Flags tab (radio button on Overview page)
- See that
my-flagcoverage shows as 41.44% for the same time interval - Bonus: Clicking into my-flag coverage brings us back to the Overview page with the flag selected, and 49.19% coverage
Expected behavior
Coverage data to match between these two views:
- Overview page with
my-flagselected my-flagcoverage value on Flags tab
Screenshots
Additional context
I was able to reproduce this.