Merging your Kernel Testing Code into KernelCI
summary
Shows how CIP’s existing CI is merged into KernelCI by adding a KCIDB client that submits JSON results (with token) and by implementing KernelCI-native LAVA jobs so existing pipelines reuse LAVA Docker orchestration and Jenkins. Demonstrates working integrations: CI results for the CIP Kernel, isar CIP core and EMLinux land in KernelCI, an RCA dashboard surfaces per-kernel logs, and an experimental automated regression detector runs; outstanding work includes filtering flaky boards and migrating to a new KernelCI API.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:57Collaborative development with OSS projects
- 9:53Framework definition
- 13:22CIP (Civil Infrastructure Platform)
- 19:56Adding test SMC (spectre meltdown)
- 20:45Lava test job
- 21:17CIP Web Dashboard
- 26:51Implementation
- 31:07Conclusion
related talks
33mMerging an existing framework into KernelCI
40mKernelCI for Embedded: Enhancing Reliability through Scalable Test Automation
40mOne year into the new KernelCI
32mBootstraping a Local KernelCI
37mKernel CI – How Far Can It Go?
33mKernel CI – How Far Can It Go?
40mGetting Started With New KernelCI CLI Tools for Automating Linux Kernel Testing...
34mLinux Kernel Testing: Providing Better Results to the Upstream Community