Description Recently we’ve been seeing Codecov report incorrect coverage deltas for pull requests. Upon inspection, I noticed that all our PRs are using the same random ~1 month old commit as the pull request base, and not one of the more recent commits with code coverage information. I inspected t…

Marking this as the solution as this is being taken offline.

Hi @tom . Thanks for looking into this! Yes, I can. There’s nothing sensitive in this one. Will this do? [Screen Shot 2020-07-22 at 17.39.40]

Hi @matej , I’m not seeing any logs for 2db4b47, which might mean that coverage reports weren’t uploaded for that commit. Would you be able to double-check to see if Buildkite attempted to run the bash script?

That job was automatically canceled, likely because the next commit came quickly after it. So there was no coverage data uploaded for that specific commit.

Incorrect base commit of pull request

Support

tom July 22, 2020, 3:22pm 2

Hi @matej, would you be able to screenshot the commit log for that pull request? I’d like to compare it to the commits here: https://codecov.io/gh/:owner:/:repo:/pull/:pull_number:/commits

Topic		Replies	Views
Nearest Pull Request Base/PseudoBase Commit not chosen correctly Bug Fixes	23	1584	September 14, 2021
Coverage is comparing with incorrect base branch Support golang , github	6	279	February 28, 2023
Incorrect coverage changes reported - base commit not uploading? Support	12	656	January 16, 2023
Selected base commit when PR is based on an older commit of the target branch Support	5	286	February 10, 2023
Comparing report to a wrong commit causes "No report found to compare against" error Support github	4	1386	February 6, 2020

Incorrect base commit of pull request

Related topics