Upstream kernel CI using patchew and TDC
summary
Demonstrates an upstream CI that uses patchew to monitor the netdev mailing list, import each patch and push it to a mirror, and a tester that boots a VM, compiles the patched kernel and runs the TDC selftest suite. Shows how a concrete unit test for the BPF action is written (control commands, expected exit code, pattern match), uses plugins (valgrind/ kmemleak, namespaces) and reports green/red results on a dashboard; current work-in-progress notes many flaky or broken TDC tests.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:48We are going to
- 1:54Motivation
- 3:48Credits to
- 4:56TC: the Linux Traffic Control tool
- 7:30Unit tests for TC: an example, with TDC
- 8:24How test cases are written (2)
- 8:51Plugins, and more test cases
- 9:33Automate it with patchew (3)
- 12:38A look at the dashboard (#1)
- 13:05Everything worked smoothly.right?
- 14:11What's next?
- 15:11Questions?
- 17:23Extra content the test script
- 17:46commits on net/sched
- 18:05why did the test fail?
related talks
26mImprove Upstream Code Quality by Bringing Testing to Patch Level
33mDPDK CI Testing Labs: New Tools, Lab Test Coverage, and DTS
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
19mChecking your work: Linux kernel testing and CI
34mLinux Kernel Testing: Providing Better Results to the Upstream Community
24mNetworking track kick-off- 38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
32mReusing the BPF CI