Oniro CI/Testing integration with LAVA
summary
Integration of LAVA with GitLab CI runs build artifacts to LAVA deploy boot test cycles and returns JUnit-format results to GitLab via REST so merge requests show pass/fail. The setup uses automatic worker provisioning and server-driven upgrades so remote workers update with no downtime. Oniro runs three remote labs — Warsaw, Belgrade, Shanghai — testing QEMU, Raspberry Pi 4, Nitrogen, Arduino Nano, blit3 and Secco v68/c61; LAVA already supports 300+ device types.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:43LAVA
- 1:17How it worked before
- 2:23Supported methods
- 3:03Supported devices
- 3:15Remote labs
- 3:53Remote labs in Oniro
- 4:39Deploying LAVA
- 5:38Demo
- 6:36Explanation
- 7:16QA Session
related talks
26mLAVA + OpenQA = Automated, Continuous Full System Testing
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned
22mLAVA community enabled testing
40mIntroduction to LAVA, the Linaro Automated Validation Architecture
56mLAVA for LITE Platforms and Tests
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA- 39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA
45mUpdate on LAVA Testing for bare metal systems