Skip to content

fix(ci): wait for all 6 test shards before Codecov posts a patch status #6386

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JSONbored merged 1 commit into from
Jul 16, 2026
+10 −0
Merged

fix(ci): wait for all 6 test shards before Codecov posts a patch status #6386

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions codecov.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,16 @@
codecov:
# Don't post a verdict until the CI run that produced the report has finished.
require_ci_to_pass: true
notify:
# The 6 backend test shards (validate-tests matrix, ci.yml) each upload their own lcov.info
# directly (flags: shard-N) -- additive by design, but Codecov re-evaluates and re-posts the
# status check after EVERY individual upload, not just the last one. Without this, codecov/patch
# can report a wildly wrong verdict (as low as ~20% "patch coverage") after only 1-2 of 6 shards
# have landed, before self-correcting once the rest arrive -- require_ci_to_pass above only checks
# the GH Actions run's own conclusion, it says nothing about upload completeness. Waiting for all
# 6 coverage uploads (JUnit test_results uploads are a separate stream and don't count here) before
# posting a status removes that premature-fail/premature-pass window entirely.
after_n_builds: 6

coverage:
status:
Expand Down