From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Matthew Jordan <matthewjordandevops@yandex.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Making package builds deterministic
Date: Thu, 7 Jul 2016 11:51:40 +0200 [thread overview]
Message-ID: <idjy45du66r.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87mvltvldb.fsf@devserver.i-did-not-set--mail-host-address--so-tickle-me>
Hi Matthew,
> After running the following commands I got some output at the end
> indicating non-determinisim.
>
> ================================================================================
>
> $ export GUIX_BUILD_OPTIONS="--keep-failed --verbosity=3"
> $ ./pre-inst-env guix build --rounds=2 go@1.4 &>/dev/stdout &>${BUILD_LOG}
>
> ...
> result of ‘/gnu/store/y89n1idbjpq0hhqjpg82mw6bd1llnl21-go-1.4.3.drv’
> differs from previous round; rejecting as non-deterministic
> @ build-failed /gnu/store/y89n1idbjpq0hhqjpg82mw6bd1llnl21-go-1.4.3.drv
> - 1 result of ‘/gnu/store/y89n1idbjpq0hhqjpg82mw6bd1llnl21-go-1.4.3.drv’
> differs from previous round; rejecting as non-deterministic
> note: keeping build directory `/tmp/guix-build-go-1.4.3.drv-0'
> guix build: error: build failed: build of
> `/gnu/store/y89n1idbjpq0hhqjpg82mw6bd1llnl21-go-1.4.3.drv' failed
>
> ================================================================================
>
> What I would like to know, is there a way to have two build/output directories
> to compare (maybe with diff or some other tool). Basically I'm just
> trying to identify the files causing the non-determinisim.
Since 7f3b2510d6b050b8fb0974fa0cd7a164ac51f6d1 the daemon should keep
the rebuilt output when “--check” and “-K” is given. Are you using the
latest version of the daemon?
~~ Ricardo
next prev parent reply other threads:[~2016-07-07 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 9:38 Making package builds deterministic Matthew Jordan
2016-07-07 9:51 ` Ricardo Wurmus [this message]
2016-07-07 10:04 ` Alex Vong
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=idjy45du66r.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=matthewjordandevops@yandex.com \
/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).