From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Andrew Tropin <andrew@trop.in>, 69284@debbugs.gnu.org
Subject: bug#69284: guix pull is not reproducible
Date: Thu, 07 Mar 2024 12:53:58 -0800 [thread overview]
Message-ID: <87bk7poja1.fsf@wireframe> (raw)
In-Reply-To: <87h6hhojo1.fsf@wireframe>
[-- Attachment #1: Type: text/plain, Size: 2987 bytes --]
On 2024-03-07, Vagrant Cascadian wrote:
> On 2024-02-20, Andrew Tropin wrote:
>> guix pull -C channels-lock.scm produces different profiles on different
>> machines.
>>
>> I executed the same command on a few different machines.
>> channels-lock.scm contains channels list with exact commit specified.
>>
>> --8<---------------cut here---------------start------------->8---
>> curl https://paste.sr.ht/~abcdw/5f18e9e5cc6cb243c84a3975eb4e6a46ed17d996 > channels-lock.scm
>> guix pull -C channels-lock.scm -p tmp
>> readlink tmp-1-link
>> --8<---------------cut here---------------end--------------->8---
>>
>> The output log on all machines starts similiar:
>> --8<---------------cut here---------------start------------->8---
>> Updating channel 'rde' from Git repository at 'https://git.sr.ht/~abcdw/rde'...
>> Authenticating channel 'rde', commits 257cebd to 2a0c7e9 (2304 new commits)...
>> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>> Authenticating channel 'guix', commits 9edb3f6 to d264237 (69420 new commits)...
>> Building from these channels:
>> guix https://git.savannah.gnu.org/git/guix.git d264237
>> rde https://git.sr.ht/~abcdw/rde 2a0c7e9
>> --8<---------------cut here---------------end--------------->8---
>>
>> --8<---------------cut here---------------start------------->8---
>> Updating channel 'rde' from Git repository at 'https://git.sr.ht/~abcdw/rde'...
>> Authenticating channel 'rde', commits 257cebd to 2a0c7e9 (2,304 new commits)...
>> Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>> Authenticating channel 'guix', commits 9edb3f6 to d264237 (2,382 new commits)...
>> Building from these channels:
>> guix https://git.savannah.gnu.org/git/guix.git d264237
>> rde https://git.sr.ht/~abcdw/rde 2a0c7e9
>> --8<---------------cut here---------------end--------------->8---
>>
>> but resulting profile is different:
>> /gnu/store/w3qq81dzdj9wckcw8fpz5lv6ylhw1m2d-profile (local fresh guix system)
>> /gnu/store/c2i8iyqkc146ac2hqzy1v6zkqs82xypp-profile (debian 11)
>> /gnu/store/svg0is4iwvlg6mgi2rvpkngcccqcvhys-profile (debian 12)
>> /gnu/store/w3qq81dzdj9wckcw8fpz5lv6ylhw1m2d-profile (remote fresh guix system)
>>
>> The first guix pull takes from 25 to 50 minutes, which is really long
>> time. However, due to irreproducibility, building the guix profile on
>> CI doesn't help to cut that time to some manageable numbers.
>
> Does passing --cores=1 help? I have found building guix (and other guile
> packages) on Debian had reproducibility issues frequently triggered by
> parallelism.
See also:
https://tests.reproducible-builds.org/debian/issues/unstable/nondeterministic_ordering_in_guile_binaries_issue.html
https://bugs.debian.org/995092
https://github.com/NixOS/nixpkgs/pull/78778
https://issues.guix.gnu.org/issue/20272
https://build.opensuse.org/request/show/732638
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-03-07 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 10:51 bug#69284: guix pull is not reproducible Andrew Tropin via Bug reports for GNU Guix
2024-03-07 20:45 ` Vagrant Cascadian
2024-03-07 20:53 ` Vagrant Cascadian [this message]
2024-03-09 8:40 ` Andrew Tropin via Bug reports for GNU Guix
2024-03-10 10:13 ` Josselin Poiret via Bug reports for GNU Guix
2024-04-08 12:49 ` Andrew Tropin via Bug reports for GNU Guix
2024-04-08 13:55 ` Simon Tournier
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=87bk7poja1.fsf@wireframe \
--to=vagrant@reproducible-builds.org \
--cc=69284@debbugs.gnu.org \
--cc=andrew@trop.in \
/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).