Skip to content

config: chromeos: enable kselftest for coverage-enabled builds #1262

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

a-wai
Copy link
Contributor

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

For now, we only run a (very) limited set of kselftests. However, enabling more of those would allow for greater code coverage. This patch creates kselftest jobs suited to running on the ChromiumOS kernel (in particular, ensuring we don't enable the ChromiumOS downstream LSM, which doesn't work with a Debian userspace).

Those tests are triggered by coverage-enabled kbuilds only, so we can eventually lower the frequency they run.

@a-wai a-wai added the staging-skip Don't test automatically on staging.kernelci.org label Jul 24, 2025
@a-wai
Copy link
Contributor Author

a-wai commented Jul 24, 2025

Draft as it needs more testing, especially regarding scheduler entries (e.g. arm64 and dt are not meant to run on x86 devices).

Also set staging-skip due to possible conflicts with other open PRs, will drop this tag once I have reviewed the scheduler entries more deeply.

@a-wai a-wai force-pushed the chromeos-enable-kselftest branch 2 times, most recently from 0f53477 to 5cf4618 Compare July 24, 2025 16:28
@a-wai
Copy link
Contributor Author

a-wai commented Jul 24, 2025

Note: this PR is on top of #1244 as it re-uses the kbuilds and anchors defined there.

@a-wai a-wai force-pushed the chromeos-enable-kselftest branch from 5cf4618 to 4de9532 Compare July 25, 2025 07:34
@a-wai a-wai removed the staging-skip Don't test automatically on staging.kernelci.org label Jul 25, 2025
For now, we only run a (very) limited set of kselftests. However,
enabling more of those would allow for greater code coverage. This
patch creates kselftest jobs suited to running on the ChromiumOS kernel
(in particular, ensuring we don't enable the ChromiumOS downstream LSM,
which doesn't work with a Debian userspace).

Those tests are triggered by coverage-enabled kbuilds only, so we can
eventually lower the frequency they run.

Signed-off-by: Arnaud Ferraris <[email protected]>
@a-wai a-wai force-pushed the chromeos-enable-kselftest branch from 4de9532 to f1f8eb9 Compare August 6, 2025 15:40
@a-wai a-wai added staging-skip Don't test automatically on staging.kernelci.org and removed staging-skip Don't test automatically on staging.kernelci.org labels Aug 20, 2025
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.

1 participant