ci(coverage): enable branch coverage and manual run#986
Merged
Conversation
Branch coverage was previously emitted as "no data found" in lcov summary output. Enable lcov branch capture across capture, filter, summary, genhtml, and extraction steps so branch metrics appear in the PR comment, step summary, and uploaded artifact. Also add workflow_dispatch so the workflow can be invoked manually after merges to develop, avoiding the wait for a release-time push to main when re-baselining coverage. Part of #953 (Step 1 of the re-baseline plan). Follow-up work to turn on BUILD_WITH_LOGGER_SYSTEM / THREAD_SYSTEM / CONTAINER_SYSTEM / MESSAGING_BRIDGE remains out of scope here; it requires adding per-system checkout and build steps analogous to the existing common_system step.
16 tasks
This was referenced Apr 24, 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
1 participant
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.
Part of #953 — Step 1 of the re-baseline plan.
Summary
coverage.yml: pass--rc lcov_branch_coverage=1to every lcov invocation (capture, filter, summary, extraction)genhtml: pass--branch-coverageso the HTML artifact shows per-branch annotationsbranch_percentage, surface it in the PR comment and step summaryworkflow_dispatch:so the workflow can be run manually ondevelopafter this merges (since the existing triggers only fire onmain/phase-*pushes and PRs targetingmain)Why
The 2026-04-13 run reported
branches...: no data found. Without branch coverage we can't measure the 70% branch-coverage criterion the parent epic was updated to target on 2026-04-16. This PR makes the measurement possible; it does not change what code is built.What this PR does NOT do
Flipping
BUILD_WITH_LOGGER_SYSTEM/THREAD_SYSTEM/CONTAINER_SYSTEM/MESSAGING_BRIDGEfrom OFF to ON is also called out as Step 1 in #953, but it requires addingCheckout+Build and installsteps for each repo (analogous to the existingcommon_systemsteps). That is a separate, larger PR and is deliberately out of scope here to keep this change low risk.Test Plan
develop(per project policy), so nothing runs automatically on this PRdevelop, invoke the workflow manually via the newworkflow_dispatchtrigger and confirm:Extract coverage percentagestep prints bothLine coverage: X%andBranch coverage: Y%(not "0%")Coverage summarystep summary shows both rowscoverage-reportartifact contains HTML with branch annotationsdevelop→mainrelease PRRisk
Low. All lcov/genhtml flags added here are additive (branch-coverage-related). If lcov rejects the flag on an edge case the
|| truefallthrough in the existing shell blocks prevents a hard failure.