the path to achieve a bug-free build on the mainline
summary
Summary of concrete outcomes and methods: build escapes are tracked across rc1–rc6 commits and attributed to specific tools so fixes map to smatch and Coverity, checkpatch and compiler warnings; a merged branch strategy creates testable branches at scale; shift-left and extra random-config coverage increase early detection; bisection is used as triage but often fails when Makefile or scripts changes expose rather than cause warnings, so patterns are recorded to filter unreliable bisects; goal is to drive closure via 0-Day CI and targeted regression tests.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 1:07Current build test status
- 5:47Goals and early detection strategies
- 9:22Bisection challenges and improvements
- 12:59Adding tests to prevent regressions
- 15:09Key challenges and proposals
- 16:15Q&A session
related talks
35mBisection: It's Not Just for Git
10mBeyond “try harder”: Effective strategies to tackle bugs
26mImprove Upstream Code Quality by Bringing Testing to Patch Level
14mCompatible Branch Coverage Driven Symbolic Execution for Efficient Bug Finding
32mBuilding Confidence Together: Continuous Integration & Testing
36mFixing Flaky Tests Like a Detective
01h 15mTaking Control Of Your Test Environment
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests