Skip to content

Add kbuild job with coverage enabled and run tests using this kernel #1131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

a-wai
Copy link
Contributor

@a-wai a-wai commented Apr 24, 2025

As we're enabling code coverage using GCOV in KernelCI, we must ensure we have a kernel with the corresponding options enabled using the coverage fragment, and also run some tests using this kernel.

The LTP tests we run on x86 Chromebooks are good candidates for helping during developement.

@a-wai a-wai force-pushed the add-gcov-kbuild-node branch from d0a85bc to d8b4a68 Compare April 24, 2025 14:57
@a-wai a-wai requested review from pawiecz and nuclearcat April 24, 2025 14:59
@a-wai a-wai force-pushed the add-gcov-kbuild-node branch from d8b4a68 to 6105c2b Compare April 30, 2025 12:53
@a-wai a-wai changed the title config: jobs: add sample kbuild job with coverage enabled Add kbuild job with coverage enabled and run tests using this kernel Apr 30, 2025
a-wai added 2 commits May 6, 2025 13:05
This job will be useful to test code coverage during development.

Signed-off-by: Arnaud Ferraris <[email protected]>
The LTP tests we already run on Chromebooks are good candidates for
initial code coverage enablement.

Signed-off-by: Arnaud Ferraris <[email protected]>
@a-wai a-wai force-pushed the add-gcov-kbuild-node branch from 6105c2b to 750eaca Compare May 6, 2025 11:05
@nuclearcat
Copy link
Member

https://staging.kernelci.org:9000/viewer?node_id=6819c63e68fedfa76d0dcaaa
coverage kernel is built, but i dont see jobs scheduled for tests

@a-wai
Copy link
Contributor Author

a-wai commented May 6, 2025

Yes, I made a mistake keeping the kselftest fragment in the previous iteration (but LTP tests explicitly require that this fragment is NOT used).

The current version should schedule the tests fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants