Hi, * Otto Kekäläinen <[email protected]> [2026-06-29 13:27]:
If developers are not quick to fix or disable failing jobs, they will develop "alert fatigue" and stop caring when the CI is red. The longer it remains red, the less likely it is to ever turn green again.
I find it really frustrating to see my CI turn red only to realize that it's just a random pipeline failure such as [1]. IMHO, these false alarms attribute to much more "alert fatigue" than your implied unwillingness of maintainers to keep their packages in good shape; especially if said packages build just fine on the buildds and pass the autopkgtests on debci.
I know not all causes of these intermittent CI failures are easily fixable (runners are a scarce resource, for example), and the last thing I want to do is lay blame at the volunteers who put in a lot of work to improve and further develop the CI pipeline. I do expect the same courtesy the other way around, though.
Cheers Timo [1] https://salsa.debian.org/cmake-team/cmake/-/pipelines/1080037 -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
signature.asc
Description: PGP signature
