Yocto Project Autobuilders and the SWAT Team
Talkat Embedded Linux Conference @ Open Source Summit North America 2022 · on Thursday, 2022-06-23· at 14:55· Griffin Hall (Level 2), JW Marriott Austin, 110 E 2nd Street Austin, TX 78701·
summary
Yocto autobuilders run on a Python CI called Billboard with a shared-state cache and source mirror, using QEMU to boot images and run LTP and p-tests; the farm has 81 builders and 26 workers across x86 and arm, and full builds take about five to nine hours. Reproducible builds succeed for ~100% of packages except golang and rubydoc, results and logs (stdout, build history, performance graphs) are published, SSDs and make’s load-awareness (-l 52) plus xz limits improve reliability, and the SWAT team closes intermittent failures (230 tracked).
AI-written summary · about
chapters (14)
- 0:00Start
- 11:38How Do You Know What Is Getting Billed by a Particular Builder
- 13:48Summary
- 16:18Performance Builders
- 17:15Matrix
- 19:17Schedulers
- 22:09Reviewing and Collecting Patches from the Mailing List
- 26:00Test Sdk
- 28:05P Tests
- 30:02Reproducible Build Results
- 31:45Build History
- 34:22The Swat Team
- 38:49Make Load Awareness
- 40:14What Needs To Be Worked on
related talks
40mI heart the Yocto Project
53mContinuous Integration and Testing of a Yocto Project Based Automotive Head Unit
32mSoftware Supply Chain with the Yocto Project
45mBuilding and Maintaining Binary Distributions with Yocto- 45mBuilding and Maintaining Binary Distributions with Yocto
20m96Boards - Autoware: 1 year on
01h 03mGetting started with Yocto Project
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA