src: send_kcidb: process coverage-report nodes - #1288
Draft
a-wai wants to merge 3 commits into
Draft
Conversation
Contributor
Author
|
Draft as it needs actual testing. |
a-wai
force-pushed
the
kcidb-bridge-coverage
branch
from
August 21, 2025 12:12
189b1ba to
f3a4797
Compare
Coverage report nodes are meant to provide global coverage percentages for a while `kbuild`, aggregating the results from individual test jobs. As such, they shouldn't be sent to KCIDB as nodes, but rather parsed in order to submit an updated build node which includes the functions/lines coverage percentages as misc fields. Add a new processing function for such nodes, which are of kind `process` and are named `coverage-report-<arch>`. Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
a-wai
force-pushed
the
kcidb-bridge-coverage
branch
from
August 22, 2025 10:20
f3a4797 to
4ed796e
Compare
Contributor
Author
|
v2:
|
Fix `_parse_coverage_node` method: 1. Fix `field_name` 2. Fix extraction of parsed build node Signed-off-by: Jeny Sadadia <jeny.sadadia@collabora.com>
JenySadadia
force-pushed
the
kcidb-bridge-coverage
branch
from
August 23, 2025 08:55
6e59907 to
bb9efa4
Compare
JenySadadia
marked this pull request as ready for review
August 23, 2025 08:55
Signed-off-by: Jeny Sadadia <jeny.sadadia@collabora.com>
Contributor
|
The KCIDB bridge is sending coverage data but KCIDB isn't able to store it since KCIDB doesn't update field data upon re-submission. |
Contributor
|
Once kernelci/kcidb#654 (comment) is implemented, we will be able to see data on KCIDB. |
a-wai
marked this pull request as draft
October 16, 2025 08:49
Contributor
Author
|
Marking as draft and setting |
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
2 participants
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.
Coverage report nodes are meant to provide global coverage percentages for a while
kbuild, aggregating the results from individual test jobs. As such, they shouldn't be sent to KCIDB as nodes, but rather parsed in order to submit an updated build node which includes the functions/lines coverage percentages as misc fields.Add a new processing function for such nodes, which are of kind
processand are namedcoverage-report-<arch>.