Keeping up with LTS: Linux Kernel Functional Testing (LKFT) on Devices
summary
Want tests that actually run on devices: describes an open-source pipeline that picks up LTS RCs within a 48-hour window, builds across compilers and architectures, dispatches ~20 lava jobs to 20–60 boards, and executes about 5,500 tests per kernel with an eight-hour reporting turnaround. Uses openembedded, LTP and kselftest, shards heavy suites, records full commit metadata for reproducibility, and reports regressions and flaky-test history for triage rather than vague promises.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 2:01Android devices
- 4:10Project LKFT
- 8:08Kernel CI vs LKFT
- 10:33LKFT Infrastructure
- 12:34Open Infrastructure
- 13:18Statistics
- 14:25LKFT T
- 15:29Reporting
- 18:54Test suites
- 21:00LTP
- 22:02Best Practices
- 24:19Android
- 26:12Keeping up with LTS
- 29:04LKFT Web UI
- 30:12Reproducibility
- 30:30Report Page
- 31:19Viewing a particular test run
- 32:11Flaky tests
- 33:45test case issue
- 34:43regressions
- 36:31getting involved
- 37:32kernel regressions
- 39:30questions
related talks
46mLinux Kernel Functional Testing, or How to Build and Test Millions of Linux Kernels
27mFaster Linux Kernel Testing with Linaro's Open-Source Tools and LKFT Automation
33mLKFT experiences and plans
36mLKFT Remote Labs
41mThe magical fantasy land of Linux kernel testing
23mExperiences and lessons we learned using kselftest and pote
34mLinux Kernel Testing: Providing Better Results to the Upstream Community- 34mLinux Kernel Testing: Providing Better Results to the Upstream Community