Create and enable post-processing job for code coverage reporting #1211
+241
−0
Conversation
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
a-wai
force-pushed
the
coverage-report-initial-template
branch
7 times, most recently
from
1eeec0d to
905de3a
Compare
|
Successfully tested on staging, as can be seen from the list of child nodes for the corresponding
|
a-wai
force-pushed
the
coverage-report-initial-template
branch
from
905de3a to
f277c92
Compare
a-wai
force-pushed
the
coverage-report-initial-template
branch
3 times, most recently
from
18f0547 to
e79ee71
Compare
pawiecz
approved these changes
Jul 22, 2025
There was a problem hiding this comment.
LGTM (from Maestro point of view, please let me know if you'd also like to have coverage reports logic double checked)
Thanks for sending the link to Nodes on Staging that verify this PR works properly
This new template is meant to be executed as a post-processing job, once every test job for a given `kbuild` node are complete. It gathers the raw coverage data from each of those test jobs and processes it as follows: * create a single JSON tracefile using `gcovr` * extract lines/functions coverage percentages for each job * create `test` child nodes for each job, reporting those percentages * merge all tracefiles in a single results file and generate both an HTML report and `lcov`-compatible tracefile; the HTML report gives a quick overview of the code coverage, while the tracefile can then be downloaded by developers for more targeted processing * create `test` child nodes for the `kbuild` job, reporting global lines/functions coverage percentages for this run Signed-off-by: Arnaud Ferraris <[email protected]>
Create a generic job definition meant for post-processing coverage data for kernel builds where GCOV support is enabled. This job is enabled for all kernels built with the `coverage` config fragment. Signed-off-by: Arnaud Ferraris <[email protected]>
a-wai
force-pushed
the
coverage-report-initial-template
branch
from
e79ee71 to
729d2b8
Compare
I'm reasonably confident with the logic, so I'd say "not mandatory", but if you have enough free cycles feel free to double check |
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.
Add a new template for generating code coverage report, meant to be used as a post-processing job for kernels built with GCOV support.
This job will collect coverage data from every test job of a given
kbuildnode, report lines/functions coverage for each job, aggregate coverage data for all jobs and generate the following artifacts pertaining to thekbuildnode itself:Depends on kernelci/kernelci-core#2908 kernelci/kernelci-core#2909 & kernelci/kernelci-core#2916