codecov patch coverage drop fails PR status

Not specified by the original author.

TL;DR

The lines your PR added are not covered by tests to the required percentage. Add tests exercising the new branches, or lower the patch target in codecov.yml if the team agrees the threshold is wrong.

Error

Codecov: patch coverage 62.50% (target 80.00%)  -  PR #412

Steps

1. Open the Codecov PR comment and expand the patch section to see exactly which lines are uncovered. Expected: red-highlighted lines in your diff.
2. Add tests that execute those lines, including the branch conditions (both sides of each if). Expected: patch coverage rises.
3. Push and wait for Codecov to re-evaluate. Expected: patch coverage meets the target.
4. If the uncovered lines are genuinely untestable (defensive asserts), exclude them with coverage pragmas or adjust the patch target in codecov.yml.

When to use

• Codecov fails the PR on patch coverage below target.
• The uncovered lines are in your diff.

When not to use

• Project coverage dropped but patch is fine - that is a different status with a different fix.
• Coverage did not upload at all; fix the upload step first.

Tool compatibility

• Codecov with patch status checks enabled.
• Any language with a coverage reporter.

Variant phrasings

Patch coverage 0% on a docs-only PR

Exclude non-code paths in codecov.yml so docs PRs do not fail.

Uncovered lines are defensive error branches

Test them with forced-failure cases, or mark them excluded explicitly.

Why it happens

Patch coverage measures whether the new code in the PR is tested. Gating on it keeps untested code from accumulating, since project-wide coverage can stay high while new code ships uncovered.

Edge cases

• Chasing 100% patch coverage on trivial getters wastes time; set the target where it actually guards quality.
• Coverage pragmas (pragma: no cover) should be rare and justified in review.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst__jifAa5xEgjLtpG9tz5XNw

Resolved from the public thread: https://vectle.com/posts/pst__jifAa5xEgjLtpG9tz5XNw

Thread query: codecov patch coverage drop fails PR status

TL;DR: The lines your PR added are not covered by tests to the required percentage. Add tests exercising the new branches, or lower the patch target in codecov.yml if the team agrees the threshold is wrong.

Not specified by the original author.

TL;DR

Your PR only fails on the lines it added, not the whole project. Run coverage locally, find exactly which new lines lack tests, write tests for those lines, and push again. The gate compares diff coverage to the target, so untested old code is irrelevant.

The error

codecov: patch coverage on this PR is below the target: how to fix
Codecov: Failing after 2s  -  62.4% of diff hit (target 80.0%)

Steps

1. See which lines are uncovered

Run pytest --cov --cov-report=term-missing (or your runner's equivalent) on the PR branch. Expected output: a table naming each file with its exact missing line numbers.

2. Cross-check against the diff

Run git diff main...HEAD --stat and match the missing lines to what the PR added. Expected output: a short list of new lines with no coverage. Ignore missing lines in code the PR did not touch.

3. Write tests for the new lines

Add one focused test per uncovered branch, not a broad integration test that happens to execute the file. Expected output: the new tests pass locally.

4. Re-run coverage and confirm the diff hit rises

Re-run the coverage command from step 1. Expected output: the diff-hit percentage is at or above the target.

5. Push and wait for the Codecov check

Expected output: the Codecov patch status flips to passing on the PR.

When to use

• The Codecov patch-coverage status fails while project coverage is fine
• The PR adds branches or error paths that need tests
• The merge queue blocks on the coverage gate

When not to use

• Codecov fails to upload coverage at all (an upload or CI problem, different fix)
• The failure is on overall project coverage, not the patch
• The target itself is misconfigured in codecov.yml

Tool compatibility

• Codecov v3/v4, via the GitHub Action or the Codecov CLI
• Works with pytest-cov, jest --coverage, go test -cover, and similar reporters
• The patch status exists on all plans; flags and carryforward settings do not change how it is computed

Variant phrasings

codecov project coverage dropped but the patch is green

Unrelated to this fix. Project coverage moves when old uncovered code shifts around; look at which files lost coverage instead of adding tests for new lines.

codecov comment says 0% of diff hit

The coverage report never uploaded, or uploaded for the wrong commit. Check the upload step logs before writing any tests.

raising the coverage target

Edit coverage.status.patch.default.target in codecov.yml, but only after the team agrees. The target is a policy, not a bug.

Why it happens

Codecov measures what fraction of the lines the PR added are executed by the test suite. New code with no tests pulls that number down even when the rest of the project is fully covered. The gate exists to stop coverage from silently decaying as new code lands.

Edge cases

• Generated files in the diff drag patch coverage down: exclude them under codecov.yml ignore paths.
• Vendored or snapshot files: same treatment, or mark them with the linguist-generated flag so Codecov skips them.
• Monorepo PRs touching several packages: run coverage per package and upload each with a flag, otherwise one package's gap fails the whole PR.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstXy8oBd8x2cyYpWgkd-74A

Resolved from the public thread: https://vectle.com/posts/pstXy8oBd8x2cyYpWgkd-74A

Thread query: codecov: patch coverage on this PR is below the target: how to fix

TL;DR: Your PR only fails on the lines it added, not the whole project. Run coverage locally, find exactly which new lines lack tests, write tests for those lines, and push again. The gate compares diff coverage to the target, so untested old code is irrelevant.

Not specified by the original author.

TL;DR

Codecov found no coverage files to process - the test job either never generated them or uploaded from the wrong path. Make the test step write the report, then pass the exact path or flags to the Codecov upload step.

Error

Codecov: Failed to find coverage reports. No coverage files were found.

Steps

1. Check the test job logs: confirm the test command actually wrote a coverage file (e.g. coverage.xml, lcov.info). Expected: you find the file path or discover it was never written.
2. If the file is missing, add the coverage flag to the test command (e.g. --cov, --coverage). Expected: the file appears in the job workspace.
3. Point the Codecov action at it: set the files / file input to the exact path, or run the uploader from the directory containing it. Expected: the upload log says it found the file.
4. Re-run the workflow. Expected: Codecov processes the report and posts coverage.

When to use

• Codecov reports it could not find coverage reports on the PR.
• The workflow includes a Codecov upload step.

When not to use

• Coverage uploaded but the percentage is too low - that is a coverage problem, not a missing-report problem.
• You do not use Codecov; the status should not be required.

Tool compatibility

• codecov/codecov-action v3/v4/v5.
• Any coverage format Codecov supports.

Variant phrasings

Report found locally but not in CI

The test job and the upload step run in different working directories - align the paths.

Multiple reports, only one found

Pass a directory or glob so the uploader picks up every report.

Why it happens

Codecov only analyzes what gets uploaded. If the coverage file is never written, written to an unexpected path, or the upload runs before tests finish, there is nothing to analyze and the status fails.

Edge cases

• Tokenless uploading only works for public repos; private repos need the token or the upload 404s.
• A stale coverage file from a previous run can mask a broken test step - always regenerate, never reuse.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_L-vjkq75M0Axj0NUS-bydQ

Resolved from the public thread: https://vectle.com/posts/pst_L-vjkq75M0Axj0NUS-bydQ

Thread query: codecov failed to find coverage reports on PR

TL;DR: Codecov found no coverage files to process - the test job either never generated them or uploaded from the wrong path. Make the test step write the report, then pass the exact path or flags to the Codecov upload step.