Merging an existing framework into KernelCI
summary
Merges the Civil Infrastructure Platform testing framework and Gentoo’s GKernelCI into KernelCI’s native system, moving a 21-board CIP lab onto KernelCI’s ecosystem of ~155 boards and ~190 builds per release; uses LAVA Docker to deploy test labs, supports a subset of kselftest and LTP, and offers results via the web dashboard and regression emails with logs and last-pass info; integration adds shared maintenance but some tests remain blocked and distribution/packaging tools stay external; experimental automatic bisection and optional KCIDB submission are part of the workflow.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:05Title
- 1:16Introduction
- 1:58Agenda
- 4:03What is KernelCI
- 5:41KernelCI Composition
- 5:59KernelCI Backend
- 9:12KernelCI Overview
- 10:33Sharing Resources
- 11:13Framework
- 13:23Kinesio Native
- 14:13Cansei Native
- 16:02Receiving Infrastructure Platform
- 16:27KernelCI Native
- 17:07CP Testing Framework
- 20:14KinesioNative
- 22:18Cansei
- 23:41Regression
- 25:32Dashboard
- 26:15Conclusion
- 27:36Documentation
- 29:02Questions
related talks
34mMerging your Kernel Testing Code into KernelCI
20mGKernelCI v.2 new features and KernelCI compatibility- 20m"GKernelCI v.2 new features and KernelCI compatibility"
40mKernelCI for Embedded: Enhancing Reliability through Scalable Test Automation
40mOne year into the new KernelCI
33mKernel CI – How Far Can It Go?
37mKernel CI – How Far Can It Go?
34mLinux Kernel Testing: Providing Better Results to the Upstream Community