Experiences and lessons we learned using kselftest and pote
summary
Linaro runs kselftest against LTS kernels on real hardware, builds test images and sends results via an email report wrapper around Squad; they add config fragments in each test and integrate header builds so tests compile reliably. Problems include tip-only test logic breaking on older kernels and several tests that hang and need maintainer fixes; plans include runtime kernel-version skip checks, switching to relative test build paths, and better tooling to avoid mixing tree-generated kubefiles.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:52Who is Anders ?
- 1:45What is kselftest?
- 2:37When do we run Kselftest
- 3:12What version Linaro runs of Kselftest and where?
- 4:13Linaro contributions to Kselftest
- 4:39Presentation icons
- 6:37Dashboard changes config changes
- 9:121: Out of tree build with a relative path
- 10:37Use a 'allmodconfig' built kernel
- 11:52Adding Kselftest to kernelCI
- 12:35Email reports on LTS and next kernels
- 14:032: Dashboard
related talks
34mLinux Kernel Testing: Providing Better Results to the Upstream Community
19mChecking your work: Linux kernel testing and CI
30mKernel Testing with KUnit: Bridging the Gap
41mKeeping up with LTS: Linux Kernel Functional Testing (LKFT) on Devices
27mFaster Linux Kernel Testing with Linaro's Open-Source Tools and LKFT Automation
46mLinux Kernel Functional Testing, or How to Build and Test Millions of Linux Kernels- 34mLinux Kernel Testing: Providing Better Results to the Upstream Community
16mKselftests augmented: running kernelspace tests from userspace