RISCV patchwork CI
summary
Pulls patches from Patchwork and reports results back, using the kernel patches daemon (KPD) to sync repos and GitHub Actions with ephemeral GitHub Runners; builds are Docker cross-compiles on aarch64 with toolchains from kernel.org. Current CI runs 12 checks (per-series and per-patch), building 32- and 64-bit kernels and flavor variants only (no full hardware boots yet), typical per-patch build latency ~20 minutes. Planned expansion to a release-style matrix (~144 builds, ~216 QEMU boots) faces VM cost, utilization, and log-parsing limits.
AI-written summary · about
chapters (16)
- 0:00Introduction to RISC-V CI
- 1:06Patchwork CI history and goals
- 3:14How the CI system works
- 5:25GitHub Actions workflow setup
- 6:46Current test coverage details
- 8:44Interpreting CI traffic lights
- 10:30Future test expansion plans
- 13:24Build optimization challenges
- 15:58Toolchain and compiler choices
- 17:28Hardware vs emulation testing
- 18:36CI response time expectations
- 20:05Performance bottlenecks
- 21:57Email notifications and support
- 22:41Pre-merge vs post-merge testing
- 24:16Series vs branch builds
- 25:41Community collaboration opportunities
related talks
32mReusing the BPF CI
36mKernelCI - How Can It Impact Your Future?
29m(Ab)using GitHub Actions for building & testing kernels
39mQuickly Test Your Kernel with GitLab CI
35mCookies for Kernel Developers
20mGKernelCI v.2 new features and KernelCI compatibility
19mUpstream kernel CI using patchew and TDC
18mSolving Pre-silicon Kernel Upstream for RISC-V First Ever