Re: Don't run Salsa CI in vain - a disabled CI is better than a persistently failing one

Chris Hofstaedtler <[email protected]> Fri, 24 Jul 2026 13:20:07 -0300
Newsgroups gmane.linux.debian.devel.general
Message-ID <[email protected]>
* Jochen Sprickerhof <[email protected]> [260724 12:50]:
>>A good example is this:
>>https://salsa.debian.org/debian/pdns-recursor/-/jobs/10005512
>>
>>Completely unactionable to me, not enabled by me, the job wasn't 
>>there when I configured salsa-ci the last time, yet now CI is red.

[..]

>I added that job to replace the old reprotest and I think it makes 
>sense given that britney uses the debrebuild results on reproduce.d.n.

Right.

>Thanks for pointing out that failed job, I can't reproduce it locally 
>and will look into it.

Thanks. Indeed I wondered if there is a "design issue" with this 
job: given the package was -just built- and thus all necessary data 
should be available, the job should not need to rely on metasnap at 
all?

Best,
Chris