Update on LAVA Testing for bare metal systems
summary
LAVA for bare‑metal systems now runs container-based test jobs on real devices, emits a standard output format for logs and parsing, and ties into Jenkins CI integration so boards get exercised from boot through firmware, kernel and userspace installs. Work reveals many devices behave differently (Samsung phones, Apple TV, black‑box appliances), some tests fail due to missing drivers or EFI quirks, and the test runner and job library exist but need wider device coverage and upstream fixes.
AI-written summary · about
chapters (8)
- 0:00Introduction to LAVA testing
- 3:41System setup and components
- 10:27Test execution and challenges
- 17:11Device interaction and automation
- 23:22Continuous integration workflow
- 28:50Debugging and troubleshooting
- 34:18Backend and monitoring
- 40:24Future improvements and Q&A
related talks
40mIntroduction to LAVA, the Linaro Automated Validation Architecture
22mLAVA community enabled testing
41mLAVA Users Forum
42mLAVA on your desk BoF
26mLAVA + OpenQA = Automated, Continuous Full System Testing
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned
33mLKFT experiences and plans
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA