On Mon Nov 4, 2024 at 2:21 PM CET, Raphael Hertzog wrote: > On Fri, 01 Nov 2024, Serafeim (Serafi) Zanikolas wrote: > > > Or maybe it would help if adequate could be run in a debusine task. We > > > already have tasks to run lintian and piuparts but we are lacking one for > > > adequate. > > > > thanks for the pointer to debusine. however it seems to be meant for > > expensive > > tasks, and adequate is not expensive at all. in my mind, the right context > > is > > autopkgtest (details in another response of mine in the same thread) > > It's not restricted to expensive tasks. And expensive depends a bit on > your point of view. Setting up a clean chroot where to install the package > and then run adequate can be considered as expensive by some developers > that would not have the proper environment ready to use. > > Which is certainly one of the reason why piuparts is also not widely used > by maintainers prior to upload. And it's precisely that kind of gap in the > test coverage that debusine wants to fill. > > I understand that autopkgtest's test infrastructure is ideal to run > adequate but I question the usefulness of adding manual tests to each > source package just to run adequate. If anything, it should hook with > something like autodep8 (i.e. auto-generated tests).
Why not create a Salsa CI job and add it to the default pipeline? I think most people who use Salsa's CI use the default pipeline, so this seems like a very low friction way of getting people to run adequate tests? Maintainers won't have to change anything on their side. The default pipeline already has a job for autopkgtest (but it doesn't seem to run adequate), lintian and piuparts, so it seems like an excellent fit.
signature.asc
Description: PGP signature
