From: Leo Famulari <leo@famulari.name>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: Guix-Help <help-guix@gnu.org>
Subject: Re: Several questions on Guix(SD)
Date: Fri, 26 Aug 2016 19:15:13 -0400 [thread overview]
Message-ID: <20160826231513.GA8782@jasmine> (raw)
In-Reply-To: <20160825230332.1b861c11@alma-ubu>
On Thu, Aug 25, 2016 at 11:03:32PM +0200, Björn Höfling wrote:
> Leo, thank you for your answers. I would like some more clarifications:
>
> On Mon, 22 Aug 2016 17:49:21 -0400
> Leo Famulari <leo@famulari.name> wrote:
> > We don't have much infrastructure for tracking reproducible builds
> > yet. Help wanted!
> >
> > We do have `guix challenge`, for challenging a binary substitute
> > server. Also, packages can be built with '--rounds=x' and '--check',
> > which repeat the build and compare the outputs to see if they are
> > bit-for-bit identical.
>
> So you mean you can't tell which builds are not reproducible? Couldn't
> Hydra just build each package two times? Or does that cost too much?
I'm not familiar with the configuration of the Hydra CI system, so I
don't know if it would be easy or hard to make it build everything twice
and check the results.
But, we would still need some infrastructure to remember the results of
the comparison, and to distinguish it from other types of failures, and
I don't _think_ we have that yet.
There is a Google Summer of Code project that aims to replace Hydra with
a Guile Scheme program called Cuirass:
https://notabug.org/mthl/cuirass
We want to support development of Cuirass until we can "dog food" it,
and then we may start building features on top of it such as a
reproducibility checker.
I've CC-ed the Cuirass author in my reply in case he has some comments.
He has also sent some reports the guix-devel mailing list that you may
find interesting.
next prev parent reply other threads:[~2016-08-26 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 20:53 Several questions on Guix(SD) Björn Höfling
2016-08-22 21:49 ` Leo Famulari
2016-08-25 21:03 ` Björn Höfling
2016-08-26 23:15 ` Leo Famulari [this message]
2016-08-26 23:23 ` Leo Famulari
2016-08-29 9:36 ` Björn Höfling
2016-08-30 12:24 ` Ludovic Courtès
2016-08-23 7:25 ` Florian Paul Schmidt
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=20160826231513.GA8782@jasmine \
--to=leo@famulari.name \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=help-guix@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.
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).