Introduction to LAVA, the Linaro Automated Validation Architecture
summary
LAVA provides an open source device farm and API that actually runs jobs described in JSON job files through an HTTP front end, scheduler and dispatcher, flashes images and recovers bricked boards automatically. The Cambridge lab holds 87 devices (≈276 ARM cores) and achieves 99% health‑check pass while supporting Jenkins/Gerrit CI, a canary pool of 16 devices, SD‑image bootloader testing, and runs 450 tests in 8 minutes with artifacts surfaced back to code review.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:03What is LAVA
- 2:54Why use LAVA
- 4:24Nexus
- 5:40Continuous Integration
- 6:06Running Tests
- 7:10Reliability
- 9:10LAVA Workflow
- 9:42LAVA HTTP
- 10:53LAVA Overview
- 12:11Inventory
- 12:56LAVA usage
- 15:05Summary
- 16:45Tyler Baker
- 18:42Calculus
- 19:24CI
- 20:06Automated test frameworks
- 21:26How did you get involved with LAVA
- 23:26LAVA Extensions
- 24:49LAVA Android Tests
- 27:22LAVA LDAP Tests
- 28:01CI Integration
- 31:07Job Files
- 31:56Garrett Events
- 34:21Overview
- 35:01Canary Testing
- 36:33Custom Rugged Devices
- 37:01Windows Mobile iOS
- 37:37Conclusion
related talks
22mLAVA community enabled testing
45mUpdate on LAVA Testing for bare metal systems
42mLAVA on your desk BoF
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned
26mLAVA + OpenQA = Automated, Continuous Full System Testing
44mAutomation beyond Testing and Embedded System Validation
07mOniro CI/Testing integration with LAVA
31mBootloader testing in LAVA