Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upTotal regression in codecov coverage report looks suspicious #35759
Labels
Comments
|
#35670 (comment) is probably relevant. cc @bcoe |
|
@puzpuzpuz @richardlau I'm not 100% sure the reason, but codecov.io seems to get a bit confused about the order that commits land to our main branch:
I believe the notifications will stabilize once it catches up. |
|
@bcoe thanks for the clarification. It makes sense. I'm going to hide the codecov message and close this issue. Feel free to reopen it if you think it's necessary. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Got an automated coverage report on #35753. The reported coverage regression is estimated as
-8.50%which is very suspicious, considering that the changes made by the PR are relatively small and tests are included. Impacted files list also includes mostly unrelated files. Is it possible that there is something wrong with codecov configuration or the service itself?See #35753 (comment) and https://codecov.io/gh/nodejs/node/pull/35753 for more details