Regression tracking & fixing: current state, problems, and next steps
summary
Automated tracking with rexbot collects regression reports from the mailing list and Bugzilla, watches for patches labeled with the link tag, and marks regressions resolved when a commit links the report; maintainers who omit link tags force manual followup. Rapid remediation often means reverting the culprit — a suspend regression lingered 12 days — so CCing the regressions mailing list and sending fixes to Linus or upstream quickly speeds stable backports and reduces wasted bisection time.
AI-written summary · about
chapters (4)
- 0:00Start
- 0:18a really quick overview of my work on regression tracking
- 7:35best practices for handling regressions
- 10:54fix regressions in reasonable time! (a) Prioritize work wrt. regression over other(') Linux kernel work
related talks
34mReporting and tracking regressions across the ecosystem
26mImprove Upstream Code Quality by Bringing Testing to Patch Level
01h 00mContinuous Regression Testing for Safer and Faster Refactoring in C++
14mThe Power of Backports : Business Impact and Automation Strategies
49mLong-Term Maintenance, or How to (Mis-)Manage Embedded Systems for 10+ Years
30mRHEL Kernel Workflow using GitLab
41mThe Importance of Continuous Regression for HW & SW Development
35mBisection: It's Not Just for Git