Skip to content

Conversation

a-wai
Copy link
Contributor

@a-wai a-wai commented Aug 21, 2025

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>.

@a-wai
Copy link
Contributor Author

a-wai commented Aug 21, 2025

Draft as it needs actual testing.

@a-wai a-wai force-pushed the kcidb-bridge-coverage branch from 189b1ba to f3a4797 Compare August 21, 2025 12:12
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 <[email protected]>
@a-wai a-wai force-pushed the kcidb-bridge-coverage branch from f3a4797 to 4ed796e Compare August 22, 2025 10:20
@a-wai
Copy link
Contributor Author

a-wai commented Aug 22, 2025

v2:

  • store coverage report and log as misc fields as well
  • don't add a log excerpt as it isn't needed

Fix `_parse_coverage_node` method:
1. Fix `field_name`
2. Fix extraction of parsed build node

Signed-off-by: Jeny Sadadia <[email protected]>
@JenySadadia JenySadadia force-pushed the kcidb-bridge-coverage branch from 6e59907 to bb9efa4 Compare August 23, 2025 08:55
@JenySadadia JenySadadia marked this pull request as ready for review August 23, 2025 08:55
Signed-off-by: Jeny Sadadia <[email protected]>
@JenySadadia
Copy link
Collaborator

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.
In this case, misc is updated for an already existing build node.
Alternate solution for the time being: kernelci/kci-dev#214

@JenySadadia
Copy link
Collaborator

Once kernelci/kcidb#654 (comment) is implemented, we will be able to see data on KCIDB.

@a-wai a-wai marked this pull request as draft October 16, 2025 08:49
@a-wai a-wai added the staging-skip Don't test automatically on staging.kernelci.org label Oct 16, 2025
@a-wai
Copy link
Contributor Author

a-wai commented Oct 16, 2025

Marking as draft and setting staging-skip as this relies on not-yet-implemented kcidb changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

staging-skip Don't test automatically on staging.kernelci.org

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants