Re: On running test suites during build - and bootstrapping issue

Jérémy Lal <[email protected]>
Newsgroups gmane.linux.debian.devel.general
Message-ID <CAJxTCxwNcs19OUBUjpmwBASC-_S3tLzrBjvKx0HHcLNnXuvggA@mail.gmail.com>
Le jeu. 28 mai 2026 à 19:00, Andreas Metzler <[email protected]> a écrit :

> On 2026-05-27 Paul Gevers <[email protected]> wrote:
> > On 5/27/26 21:39, Jérémy Lal wrote:
> > > running a test suite during build is something that feels more and more
> > > useless, given debci.
>
> > In my view, build time tests and as-installed tests serve different
> > purposes.
>
> > During build, you want to ensure that what you build is indeed working
> and
> > you want to prevent installing a broken package.
>
> > As-installed tests ensure that *what is installed* works *and keeps on
> > working* in the ecosystem it lives in. A lot of packages run the same
> set of
> > tests, but that's not necessarily the right choice.
>
> Also build-time tests are cheap compared to CI since they only run once
> per arch.
>
> cu Andreas
>

Could sbuild have an option that enables the various build profiles that
are available in debian/control
(thinking about nocheck, nodoc, in particular, but possibly some others)
if building with default build profile (none) fails because some package,
that is present in the control file with a <!profile>, is missing on a
specific arch ?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.