The issue is that we don't have a process to deal with CI failures of all drivers quickly and effectively. Once we do, it should be smooth sailing and we can keep everything.
First of all, no contributor to shared code is required to fix issues in all drivers that their commit breaks. The goal is to stop using the pre-merge CI as a justification to force unrelated contributors to work on all drivers just because they are contributors. It would be a bit exploitative to assume that every contributor must debug all drivers that turn red due to a change. I think I understand that well because I have debugged 5+ drivers by myself in the past that are not my responsibility to maintain, and it does feel exploitative. Therefore, we could establish that each driver/HW combo in pre-merge CI has the following options: 1) a contact person for prompt CI issue resolution 2) unconditional xfail by the author (or removal from pre-merge CI if logs lack the information necessary to add xfail) If (2) is the chosen option, we could say that such drivers shouldn't be in pre-merge CI at all because what's the point of that if we just keep adding xfail. Instead, the interested parties could just run tests nightly/weekly/monthly manually and add the xfails themselves. That would leave only those driver/HW combos in pre-merge CI that have a contact person. Marek On Thu, Apr 30, 2026 at 10:16 AM Mike Blumenkrantz <[email protected]> wrote: > > Hi all, > > It's that time again. I've created an issue to discuss the possibility of > splitting parts of mesa off into another repo: > > https://gitlab.freedesktop.org/mesa/mesa/-/work_items/15365 > > > Mike
