From: zimoun <zimon.toutoune@gmail.com>
To: Brice Waegeneire <brice@waegenei.re>,
Lo Peter <peterloleungyau@gmail.com>
Cc: Help-Guix <help-guix-bounces+brice+lists=waegenei.re@gnu.org>,
help-guix <help-guix@gnu.org>
Subject: Re: How to debug / investigate non-reproducible build for r-repr?
Date: Mon, 29 Jun 2020 12:19:39 +0200 [thread overview]
Message-ID: <86lfk6b2dg.fsf@gmail.com> (raw)
In-Reply-To: <69720a2c9c1f94cdf5e576ac81f12053@waegenei.re>
Dear,
To complement what Brice said.
On Mon, 29 Jun 2020 at 09:13, Brice Waegeneire <brice@waegenei.re> wrote:
> --8<---------------cut here---------------start------------->8---
> $ guix build r-repr --check --keep-failed
> …
> guix build: error: derivation
> `/gnu/store/5rbf3kb0s96m1nij5s631j1k3mnh75lg-r-repr-1.1.0.drv' may not
> be deterministic: output
> `/gnu/store/aah5bpxg1h3sf09ca1plp4cbj745n95y-r-repr-1.1.0' differs from
> ‘/gnu/store/aah5bpxg1h3sf09ca1plp4cbj745n95y-r-repr-1.1.0-check’
> --8<---------------cut here---------------end--------------->8---
Before going to "diffoscope", personally I try to identify which files
are offending, something like:
--8<---------------cut here---------------start------------->8---
diff -r --no-dereference /gnu/store/75xc2l38ml4mz7w2cb4qhg08vs34xr3i-r-repr-1.1.0{,-check}
Binary files /gnu/store/75xc2l38ml4mz7w2cb4qhg08vs34xr3i-r-repr-1.1.0/site-library/repr/R/repr.rdb and /gnu/store/75xc2l38ml4mz7w2cb4qhg08vs34xr3i-r-repr-1.1.0-check/site-library/repr/R/repr.rdb differ
Binary files /gnu/store/75xc2l38ml4mz7w2cb4qhg08vs34xr3i-r-repr-1.1.0/site-library/repr/R/repr.rdx and /gnu/store/75xc2l38ml4mz7w2cb4qhg08vs34xr3i-r-repr-1.1.0-check/site-library/repr/R/repr.rdx differ
--8<---------------cut here---------------end--------------->8---
Well, you need to check the files "repr/R/repr.{rdb,rdx}". Because of
the option "--keep-failed", you can go to
"/tmp/guix-build-r-repr-1.1.0.drv-0" and give a look to how these files
are produced. The classical source of non-determinism is date. Then if
everything appears to you as expected, then you can go to "diffoscope".
Hope that helps,
simon
prev parent reply other threads:[~2020-06-29 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 8:25 How to debug / investigate non-reproducible build for r-repr? Lo Peter
2020-06-29 9:13 ` Brice Waegeneire
2020-06-29 10:19 ` zimoun [this message]
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=86lfk6b2dg.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=brice@waegenei.re \
--cc=help-guix-bounces+brice+lists=waegenei.re@gnu.org \
--cc=help-guix@gnu.org \
--cc=peterloleungyau@gmail.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.
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).