Reusing the BPF CI
summary
The CI automatically turns mailing-list patches into GitHub pull requests, Patchwork-to-PR conversion, and injects a middle commit that copies files from a general-patches-vmtest repo including .github/workflows/test.yml so GitHub Actions run the exact VM-test workflow. It builds a rootfs, drops in tools, runs tests under QEMU (BPF selftests, test_progs, maps), reports back to Patchwork, and recently hit a break when a self-hosted runner enforcement change prevented GitHub runners — proposals include consolidating scripts, a reusable vmtest GitHub Action, and stable guaranteed workflows.
AI-written summary · about
chapters (6)
- 0:00Introduction to BPF CI
- 7:55Reusing BPF CI for development
- 11:26Initial success and limitations
- 16:03Making CI easier to reuse
- 21:02Q&A and future directions
- 31:16Closing remarks
related talks
26mRISCV patchwork CI
29m(Ab)using GitHub Actions for building & testing kernels
26mImprove Upstream Code Quality by Bringing Testing to Patch Level
19mUpstream kernel CI using patchew and TDC
14mUsing packit and testing farm for CI/CD and automation in an upstream project
45mA Call to (GitHub) Actions!
36mKernelCI - How Can It Impact Your Future?
20mHow to Setup Test Infrastructure