Day-to-day Testing of Linux 'Next' Kernel Branch - My Story
summary
Daily automation runs kernel images from linux-next, boots them on a ~30 single-board computers test farm controlled over UART with power switches via USB CDC GPIO, captures logs and stack traces, and runs an expect-driven test script that returns pass/fail codes. Regression hunting uses git bisect + scripted tests plus stash/revert tricks to isolate multiple regressions; reports include hardware, config, reproducer and oops. Results: since v4.15 roughly 250 Tested-by / 90 Reported-by tags and over 100 reported commits in 5.19.
AI-written summary · about
chapters (4)
related talks
41mThe magical fantasy land of Linux kernel testing
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto
34mLinux Kernel Testing: Providing Better Results to the Upstream Community
41mKeeping up with LTS: Linux Kernel Functional Testing (LKFT) on Devices
27mFaster Linux Kernel Testing with Linaro's Open-Source Tools and LKFT Automation
39mRegression Testing Boot-time Performance in the Linux Kernel
26mImprove Upstream Code Quality by Bringing Testing to Patch Level
46mLinux Kernel Functional Testing, or How to Build and Test Millions of Linux Kernels
