From: Ryan Prior <rprior@protonmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, guix-devel@gnu.org
Subject: Re: Caching test results separately?
Date: Mon, 13 Mar 2023 22:44:42 +0000 [thread overview]
Message-ID: <ieDw-EZQGI2jXZAFZomrWR0Bzex0Fu33Dr0cgktwhbknlksdUONcx1Kejhs88NJ3jT-dYBfhwp_-Y7qEbgjNqYE04bk7T7ZoA_dQSbIAFsc=@protonmail.com> (raw)
In-Reply-To: <871qlsi97h.fsf@jpoiret.xyz>
------- Original Message -------
On Monday, March 13th, 2023 at 10:21 PM, Josselin Poiret <dev@jpoiret.xyz> wrote:
> But I would really like for tests to move out of build phases
I've mentioned this previously in IRC as well. Fundamentally, it strikes me as wrong that a change which only affects tests, leaving the installed package the same byte for byte, should require a full package re-build.
An improvement would be to treat tests, and their pass/fail status, are metadata separate from package builds. In Eelco's thesis, testing is described as a major motivator for nix: but in his construction, nix's role is to produce package builds, and then you run tests on the outputs to decide whether to promote a build into production or not. We should use Guix to create testing, staging and production deployments, not to gatekeep and prevent packages with failing tests from building.
Many packages I've created or upgraded had some or all tests disabled because they require a network stack, eg a client library for postgres requires a postgres server. This should be easy to model using Guile and Guix. I would love to contribute to development in this direction.
Ryan
next prev parent reply other threads:[~2023-03-13 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 18:31 Caching test results separately? Dr. Arne Babenhauserheide
2023-03-13 22:21 ` Josselin Poiret
2023-03-13 22:44 ` Ryan Prior [this message]
2023-03-13 23:10 ` Towards generalized testing (Was: Caching test results separately?) Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-14 11:03 ` Caching test results separately? Simon Tournier
2023-03-16 14:08 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ieDw-EZQGI2jXZAFZomrWR0Bzex0Fu33Dr0cgktwhbknlksdUONcx1Kejhs88NJ3jT-dYBfhwp_-Y7qEbgjNqYE04bk7T7ZoA_dQSbIAFsc=@protonmail.com' \
--to=rprior@protonmail.com \
--cc=arne_bab@web.de \
--cc=dev@jpoiret.xyz \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).