System test manifest

System test manifest

[Ludovic Courtès]

Hello Guix!

Commit 5ec4156bbcaec8337f78411204d59e59e706103b adds a manifest for
system tests.  Now “make check-system” simply does:

  ./pre-inst-env guix build -m etc/system-tests.scm

The nice thing is that it’s more flexible than the custom script we had
since it gives access to all the command-line options.

As a bonus (this is directly inspired by discussions in the “release”
working group at the Guix Days), you can pass it to ‘guix weather’ to
get test coverage data.  There are probably a couple of things to
improve in ‘guix weather’ to make it more convenient, such as adding a
flag to list missing substitutes.

My next goal is to have a manifest for “release-critical things” that
one can again pass to ‘guix build’ or ‘guix weather’ to have an
immediate picture of the “releasability” status.

Feedback welcome!

Ludo’.

Re: System test manifest

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

Thanks!

Ludovic Courtès <ludo@gnu.org> writes:

> There are probably a couple of things to
> improve in ‘guix weather’ to make it more convenient, such as adding a
> flag to list missing substitutes.

That'd be great indeed!

> My next goal is to have a manifest for “release-critical things” that
> one can again pass to ‘guix build’ or ‘guix weather’ to have an
> immediate picture of the “releasability” status.

Do we already know what the critical things are?  I guess we need a list
of popular packages, right?

Maybe this? https://pkgstats.archlinux.de/packages

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: System test manifest

[Ludovic Courtès]

Hi,

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>> My next goal is to have a manifest for “release-critical things” that
>> one can again pass to ‘guix build’ or ‘guix weather’ to have an
>> immediate picture of the “releasability” status.
>
> Do we already know what the critical things are?  I guess we need a list

“make assert-binaries-available” has a short list of critical packages,
but we could certainly improve on that.

Ludo’.