Automated Testing & Board Farming
summary
Lab infrastructure migrates the coordinator to a gRPC coordinator and adds small Linux test‑controller boards to replace flaky USB hubs, enabling the exporter/place model where exporters only expose resources and places combine them. CI and interactive flows converge via strategy-based reprovisioning that always flashes bootloader/kernel/rootfs, letting iterative kernel rebuilds and reflashes happen in seconds in local loops (fast local kernel loop ~seconds). Real deployments include ~30 boards per lab and racks with 16 boards each; tooling tradeoffs vs Lava center on scheduler vs interactive control (exporter/place model).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:50Current projects and tools
- 13:36GPIO handling challenges
- 18:14Board availability and testing
- 24:57Build systems and artifacts
- 30:19File system snapshots
- 33:33Standardizing boards and docs
- 37:28Resource sharing and multi-node
- 41:21LAVA versus Lab Grid
- 42:48Closing remarks
related talks
40mBoF: Automated Testing and Board Farming
33mAutomated Testing for Embedded Development: Next Generation Board Farming
36mFarming Together
44mAutomation beyond Testing and Embedded System Validation
35mTest Harness: Continuous Testing on Hardware
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned
36mLKFT Remote Labs
22mHardware in the loop pipelines for testing - for everyone!