LAVA community enabled testing
summary
LAVA Federation runs daily tests by spinning up the latest server and dispatcher Docker images and connecting them to community labs so CI can borrow real boards, run functional jobs, collect logs and return hardware when done. The system supports many boot methods (22) and an expanding pool of device types (about 150 device types overall) but currently exercises only two remote labs and roughly five device types with ~10 jobs; results expose regressions and feature coverage. LAVA Federation uses only LAVA jobs and APIs.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:36What is LAVA?
- 1:29Testing without LAVA
- 3:29Testing with LAVA (full lab)
- 4:17Testing with LAVA (user side)
- 5:59Supported methods deploy
- 6:21Supported boards: 150
- 6:45Combinatorial nightmare
- 7:32lavafed goals
- 9:08lavafed architecture
- 13:09lavafed current status
- 13:42lavafed future: features
related talks
40mIntroduction to LAVA, the Linaro Automated Validation Architecture
42mLAVA on your desk BoF
45mUpdate on LAVA Testing for bare metal systems
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned
41mTesting with Volcanoes - Fuego+LAVA Going Distributed
26mLAVA + OpenQA = Automated, Continuous Full System Testing
07mOniro CI/Testing integration with LAVA
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA