Integrating testing with maintainer flows
summary
Argues for a single, parseable test output so CI can run and index results by SHA1, already implemented as a git-indexed CI with a git-log view of test results; shows a trivial Python conversion path from junit XML to ktap and recommends shipping test artifacts (dmesg, core files, tar.xz) to cloud storage. Notes xfs tests need expertise and can run a smoke suite in ~30 minutes while full configs take 2.5–4 hours, and some tests fail only 1-in-200 or 1-in-800 times.
AI-written summary · about
chapters (6)
- 0:00Welcome and introduction
- 1:45Problem space in testing
- 8:07Test output formats and artifacts
- 15:41Dream of common test infrastructure
- 22:47Standardizing test requirements
- 27:21Interpreting test failures
related talks
50mTips for Writing Good Tests for Linux
15m"Linux Testing made better with DATA"
45mRunning Tests in Continuous Integration
33mIntentional and Unintentional Compromises in Test Automation
33mKernel CI – How Far Can It Go?
35mTurning test writing into a consistently brief and pleasant experience
37mKernel CI – How Far Can It Go?
30mKernel Testing with KUnit: Bridging the Gap