From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Treating tests as special case
Date: Thu, 5 Apr 2018 18:41:58 +0200 [thread overview]
Message-ID: <20180405164158.GA965@thebird.nl> (raw)
In-Reply-To: <87vad5y8v7.fsf@gnu.org>
On Thu, Apr 05, 2018 at 05:24:12PM +0200, Ludovic Courtès wrote:
> Pjotr Prins <pjotr.public12@thebird.nl> skribis:
>
> > I am *not* suggesting we stop testing and stop writing tests. They are
> > extremely important for integration (thought we could do with a lot
> > less and more focussed integration tests - ref Hickey). What I am
> > writing is that we don't have to rerun tests for everyone *once* they
> > succeed *somewhere*. If you have a successful reproducible build and
> > tests on a platform there is really no point in rerunning tests
> > everywhere for the exact same setup. It is a nice property of our FP
> > approach. Proof that it is not necessary is the fact that we
> > distribute substitute binaries without running tests there. What I am
> > proposing in essence is 'substitute tests'.
>
> Understood.
>
> > If tests are so important to rerun: tell me why we are not running
> > tests when substituting binaries?
>
> Because you have a substitute if and only those tests already passed
> somewhere. This is exactly the property we’re interested in, right?
Yup. Problem is substitutes go away. We don't retain them and I often
encounter that use case.
Providing test-substitutes is much lighter and can be retained
forever.
When tests ever pass on a build server, we don't have to repeat them.
That is my story.
Pj.
next prev parent reply other threads:[~2018-04-05 16:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 5:24 Treating tests as special case Pjotr Prins
2018-04-05 6:05 ` Gábor Boskovits
2018-04-05 8:39 ` Pjotr Prins
2018-04-05 8:58 ` Hartmut Goebel
2018-04-05 6:21 ` Björn Höfling
2018-04-05 8:43 ` Pjotr Prins
2018-04-06 8:58 ` Chris Marusich
2018-04-06 18:36 ` David Pirotte
2018-04-05 10:14 ` Ricardo Wurmus
2018-04-05 12:19 ` Björn Höfling
2018-04-05 14:10 ` Ricardo Wurmus
2018-04-05 10:26 ` Ricardo Wurmus
2018-04-05 14:14 ` Ludovic Courtès
2018-04-05 14:59 ` Pjotr Prins
2018-04-05 15:17 ` Ricardo Wurmus
2018-04-05 15:24 ` Ludovic Courtès
2018-04-05 16:41 ` Pjotr Prins [this message]
2018-04-05 18:35 ` Pjotr Prins
2018-04-06 7:57 ` Retaining substitutes Ludovic Courtès
2018-04-05 20:26 ` Treating tests as special case Mark H Weaver
2018-04-06 6:06 ` Pjotr Prins
2018-04-06 8:27 ` Ricardo Wurmus
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=20180405164158.GA965@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=ludo@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).