LKFT experiences and plans
summary
LKFT provides an automated pipeline: git push triggers Jenkins builds for six kernel/AOSP branches, artifacts go to snapshots and LAVA runs tests on multiple boards; results are curated before upstream. Current scale hits ~14,000 tests per build and up to ~50,000 test cases for AOSP. Major pain points are false positives, flaky hardware (USB/serial resets, SD card wear), and test-suite mismatches (LTP/kselftest assumptions). Planned fixes: more hardware, second UARTs, staging lab, unified logging and bisection; tools: Jenkins + LAVA + fastboot-based flashing.
AI-written summary · about
chapters (12)
- 0:00Introduction to LKFT
- 1:12Project background and goals
- 2:17Current LKFT system overview
- 6:15Early challenges and problems
- 9:13Hardware lab setup issues
- 12:10Reporting automation limitations
- 13:58Future hardware improvements
- 16:51Stability and reliability plans
- 17:57Test coverage and reporting
- 20:28Software and UI improvements
- 21:58Open discussion and priorities
- 22:38Q&A session begins
related talks
41mKeeping up with LTS: Linux Kernel Functional Testing (LKFT) on Devices
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
24mContinuously Integrating the Upstream Linux Kernel on Hardware
45mUpdate on LAVA Testing for bare metal systems
40mIntroduction to LAVA, the Linaro Automated Validation Architecture
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned
48mLiving on Master: Using Yocto Project, Jenkins and LAVA for a Rolling Release