unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: Install FAQ: Only build the non-deterministic packages?
Date: Mon, 19 Sep 2016 17:47:08 -0400	[thread overview]
Message-ID: <20160919214708.GE10174@jasmine> (raw)
In-Reply-To: <874m5cno73.fsf@we.make.ritual.n0.is>

On Mon, Sep 19, 2016 at 11:06:40AM +0000, ng0 wrote:
> Leo Famulari <leo@famulari.name> writes:
> > Basically, we need someone to be a reproducibility champion in Guix! We
> > have all the tools to test reproducibility, but somebody needs to
> > implement a system to actually perform the tests automatically
> 
> Do we have comparable tests available in th test suite of guix?
> If not, I'll open a bug on this so that someone with competence in the
> test suite can put it on their todo list.

Since this test would involve building every package at least twice, I
think it wouldn't be possible for most users who would run `make check`.

> > , store the results, and make the results available to users.
> 
> Could Cuiriass - or what our soon-to-be-replacement of hydra is called
> again - do this? Have one testing checkout where all the packages will
> be run again the test(s) we created before and then process the build
> logs?

Right, I think that testing all the packages for reproducibility is best
done by the continuous integration server, whether Hydra or Cuirass. The
CI server can perform the tests on a variety of build farm machines,
record the results, and present them to users somehow.

  reply	other threads:[~2016-09-19 21:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 17:11 Install FAQ: Only build the non-deterministic packages? carlo von lynX
2016-09-17 23:35 ` Leo Famulari
2016-09-19 11:06   ` ng0
2016-09-19 21:47     ` Leo Famulari [this message]
2017-01-12 23:58 ` carlo von lynX
2017-01-13 13:14   ` Ludovic Courtès
2017-01-20 15:55     ` carlo von lynX

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=20160919214708.GE10174@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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).