CI: Coverage: Fix: Change the source of component name. #93496
+1
−1
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.
Getting Component Name from Testsuite Name Instead of Testcase Identifier
This pr modifies the way the component name is derived for coverage report generation. Previously, the script extracted the component name from the testcase identifier, assuming it followed the format:
However, after commit 9219c81 (twister: make no-detailed-test-id default), the level of detail in test identifiers was reduced.
Example change in identifiers:
Before (detailed):
After (reduced):
Because of this, the script incorrectly interprets
cap_commander_test_broadcast_reception
as the component name instead of the correctbluetooth
. This leads to the following issue when generating the coverage report:(Example failure: GitHub Actions log)
This change updates the logic to derive the component name from the testsuite name rather than testcase identifier, restoring correct component mapping and preventing coverage report generation failures.
Probe run:
https://github.com/zephyrproject-rtos/zephyr/actions/runs/16442311600?pr=93496