7 Ways to Make Kernel Developers Like Cookies
summary
Red Hat’s Continuous Kernel Integration (“cookie”) runs thousands of tests across hundreds of Beaker hosts in parallel, builds with Koji/Koji-like farms and publishes kernels so maintainers can reproduce failures, and already uncovers real upstream bugs. It uses wave tests to isolate flaky runs, a dynamic bad-host list to skip unreliable machines, a manual review gate that filters infrastructure noise before mailing-list reports, and a central data warehouse plus contributions to the kernelci DB for standardized results and metrics.
AI-written summary · about
chapters (4)
related talks
35mCookies for Kernel Developers
08mKeynote: Kevin Hilman in conversation with Greg Kroah-Hartman
33mKernel CI – How Far Can It Go?
35mKeeping the linux kernel secure across 10+ RHEL releases
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
36mLinux Kernel Building, Testing, and Deployment at Facebook
29m(Ab)using GitHub Actions for building & testing kernels
24mContinuously Integrating the Upstream Linux Kernel on Hardware