Hi, On 2026-06-09 at 17:05+02:00, Gabriel Wicki wrote: > We could define modules (or packages) and map them to the tests that > should pass to give the green light for merging?
This would be lovely! For sysadmin packages often I had to grep gnu/services for the service name _then_ gnu/tests for the relevant tests. On 2026-06-09 at 17:05+02:00, Gabriel Wicki wrote: > For the other, more technical questions you raise, I wonder whether we > could make our guix-cuirass-bot run specific (system) tests for certain > package updates? It should be clear that updating GRUB requires systems > booting after the patch. This is—as you describe—rather cumbersome to > do manually, can be done automatically and should not be expected of > contributors and team members to be done on their laptops. Just wanna chime in that currently the ETA for CI is wildly erratic (could take hours, days, or weeks to report the result), hence it's likely that someone should be running the tests locally (e.g. -P1 builds, system tests) where reasonable to not make the review round trips daunting to contributors. Or at least personally, if I submit a patch I'd rather be told to run moderately expensive tests instead of waiting undeterministically for CI results, but it could be just me. Cheers, Phong
