From: Christopher Baines <mail@cbaines.net>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: package submission, unit test failures on Guix QA... policies?
Date: Mon, 10 Jun 2024 10:30:05 +0100 [thread overview]
Message-ID: <871q5516xu.fsf@cbaines.net> (raw)
In-Reply-To: <CAJsg1E-OQ8dcV0hvqJ3hJp4-6WCAhv=YQaUXdYamWhYxZe+JXQ@mail.gmail.com> (Andy Tai's message of "Fri, 7 Jun 2024 10:37:55 -0700")
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Andy Tai <atai@atai.org> writes:
> Hi, I have a patch submission that builds fine (in the GNU Guix sense,
> that is, unit tests run and pass) locally but fails on Guix QA due to
> unit tests failing.
>
> I suspect that the failures are due to the build machine (or machines)
> as plain x86-64 PC (fine as build server(s)) does not have exotic
> hardware units like GPU that the package in question is meant to use.
>
> This may become more common as GPU and NPU applications become more popular.
>
> Curious how shall such cases be handled? Maybe reviewers can build
> and run the patch to verify the patch works, so the Guix QA failure
> can be overridden?
I'm not sure we have great guidance here, but viewing this through the
reproducible builds lens, we want packages to build identically across a
diverse range of setups.
While tests might not affect the outputs, I think the same premise still
holds. The set of tests that are run should be the same regardless of
the machine used.
Have you got some specific examples where you're seeing failing unit
tests, only on headless servers?
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2024-06-10 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 17:37 package submission, unit test failures on Guix QA... policies? Andy Tai
2024-06-07 23:56 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-10 9:30 ` Christopher Baines [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871q5516xu.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=atai@atai.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.