From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: 55822@debbugs.gnu.org
Subject: bug#55822: option to run diffoscope with guix build --rounds=N and --check
Date: Mon, 06 Jun 2022 14:09:23 -0700 [thread overview]
Message-ID: <87tu8xfqik.fsf@contorta> (raw)
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
When I do:
guix build --rounds=2 PACKAGE
And the results differ, the process of actually running diffoscope on
the results is very manual and a bit hard to automate. I might get
output like:
guix build: error: derivation
`/gnu/store/dn50zya4d1zh21q6s3nh7f394s7ksknv-autogen-5.18.16.drv' may
not be deterministic: output
`/gnu/store/04byv4py1firka28h3nl70bj1g0a3n6k-autogen-5.18.16' differs
from
?/gnu/store/04byv4py1firka28h3nl70bj1g0a3n6k-autogen-5.18.16-check?
First of all, I have to actually remember to run:
guix build --rounds=2 --keep-failed PACKAGE
Would it be crazy for --rounds=N resonably assume --keep-failed ?
Then it'll actually keep the produced /gnu/store/*-check ... then I have
to screen-scrape the right files, sometimes accidentally grabbing the
.drv instead of the right directory, and pass both the regular store
item and the /gnu/store/*-check item ... if i get everything right I end
up with:
diffoscope /gnu/store/HASH-PACKAGE-VERSION /gnu/store/HASH-PACKAGE-VERSION-check
And that basically works... but it is a very manual process...
guix already has a similar tool to handle this sort of thing:
guix challenge --diff=diffoscope PACKAGE
But that assumes you are comparing things from your local build and the
substitute server or servers, not two locally built things.
How plausible would it be to implement something simile to "guix
challenge --diff=diffoscope" like:
guix build --rounds=2 --keep-failed --diff=diffoscope
(or could --diff=diffoscope *assume* --keep-failed ?)
Oh, and... basically all of the above applies for:
guix build --check PACKAGE
e.g. --keep-failed by default, option to support --diff=diffoscope, etc.
Thanks for considering!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
reply other threads:[~2022-06-06 21:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87tu8xfqik.fsf@contorta \
--to=vagrant@reproducible-builds.org \
--cc=55822@debbugs.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).