Repository navigation
ci: compare unit coverage against the coverage-history branch - #1024
Merged
Merged
Conversation
Coverage (unit tests)Compared against
Line and branch coverage from unit test reports. History is recorded on the |
Contributor
Code Coverage
|
The coverage history moved from main to the coverage-history branch, but the unit coverage comment still read coverage/history.csv from the checkout. It no longer exists, so every PR comment said no baseline was recorded. Fetch history.csv from coverage-history before comparing; if that fails, compare still falls back to absolute numbers. Also fix the comment footer, which still pointed at coverage/history.csv.
kikoso
force-pushed
the
ci/unit-coverage-baseline
branch
from
October 1, 2026 19:02
a8c6474 to
dd88f44
Compare
dkhawk
approved these changes
Oct 1, 2026
This was referenced Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The unit coverage comment on every PR says "No unit baseline recorded in
coverage/history.csvyet" and only shows absolute numbers. The coverage history moved frommainto thecoverage-historybranch, buttest.ymlstill runscompareagainstcoverage/history.csvin the checkout, which no longer exists.Fix
compare, fetchhistory.csvfromcoverage-historyand pass it with--csv. If the fetch fails,comparefalls back to absolute numbers as today, and the step is alreadycontinue-on-error.coverage/history.csv; it now points at thecoverage-historybranch.Testing
Ran the same fetch and
comparelocally against current unit reports. The comment now reads "Compared against109b74aonmain(#1020)" with a change column per module instead of the no-baseline message. This PR's own coverage comment should show the same.