GNU bug report logs -
#74204
Guix is not reproducible
Previous Next
Reported by: Jakob Kirsch <jakob.kirsch <at> web.de>
Date: Mon, 4 Nov 2024 18:39:01 UTC
Severity: normal
Done: Hilton Chain <hako <at> ultrarare.space>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 74204 in the body.
You can then email your comments to 74204 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#74204
; Package
guix
.
(Mon, 04 Nov 2024 18:39:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jakob Kirsch <jakob.kirsch <at> web.de>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Mon, 04 Nov 2024 18:39:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
I've recently noticed that `guix challenge guix` fails since guix isn't reproducible at the moment. As someone pointed out on XMPP, this is due to parallelism issues with Guile so running `guix build guix --no-grafts --cores=1 --check` reliably produces the same output.
I've sent a simple patch in #74112 to address this and I think this is important since the main guix package should definitely be reproducible so it can be trusted.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#74204
; Package
guix
.
(Tue, 05 Nov 2024 10:32:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 74204 <at> debbugs.gnu.org (full text, mbox):
Hi Jakob,
On Tue, 05 Nov 2024 02:38:34 +0800,
Jakob Kirsch via Bug reports for GNU Guix wrote:
>
> I've recently noticed that `guix challenge guix` fails since guix isn't
> reproducible at the moment. As someone pointed out on XMPP, this is due to
> parallelism issues with Guile so running `guix build guix --no-grafts
> --cores=1 --check` reliably produces the same output.
>
> I've sent a simple patch in #74112 to address this and I think this is
> important since the main guix package should definitely be reproducible so it
> can be trusted.
I can confirm the reproducibility issue.
I have two x86_64-linux machines building guix to verify the fix, I'll apply
your patch once they produce matching outputs.
Thanks for reporting!
Reply sent
to
Hilton Chain <hako <at> ultrarare.space>
:
You have taken responsibility.
(Tue, 05 Nov 2024 15:26:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jakob Kirsch <jakob.kirsch <at> web.de>
:
bug acknowledged by developer.
(Tue, 05 Nov 2024 15:26:03 GMT)
Full text and
rfc822 format available.
Message #13 received at 74204-done <at> debbugs.gnu.org (full text, mbox):
Hello again,
On Tue, 05 Nov 2024 18:31:04 +0800,
Hilton Chain via Guix-patches via wrote:
>
> Hi Jakob,
>
> On Tue, 05 Nov 2024 02:38:34 +0800,
> Jakob Kirsch via Bug reports for GNU Guix wrote:
> >
> > I've recently noticed that `guix challenge guix` fails since guix isn't
> > reproducible at the moment. As someone pointed out on XMPP, this is due to
> > parallelism issues with Guile so running `guix build guix --no-grafts
> > --cores=1 --check` reliably produces the same output.
> >
> > I've sent a simple patch in #74112 to address this and I think this is
> > important since the main guix package should definitely be reproducible so it
> > can be trusted.
>
> I can confirm the reproducibility issue.
>
> I have two x86_64-linux machines building guix to verify the fix, I'll apply
> your patch once they produce matching outputs.
Took me quite a while to build 5 rounds. :)
--8<---------------cut here---------------start------------->8---
$ guix hash --serializer=nar /gnu/store/fs7x07jfn7igpkwv3alrs9by21q70y13-guix-1.4.0-26.5ab3c4c
0kh87wb4qn97kwzrf4igal71cjvv143j6jr2y3dwfzcy1madj1ll
--8<---------------cut here---------------end--------------->8---
Applied #74112 as 4c56d0cccdc44e12484b26332715f54768738c5f, thanks!
Information forwarded
to
bug-guix <at> gnu.org
:
bug#74204
; Package
guix
.
(Thu, 07 Nov 2024 17:57:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 74204-done <at> debbugs.gnu.org (full text, mbox):
Hi,
On Tue, 05 Nov 2024 at 23:25, Hilton Chain via Bug reports for GNU Guix <bug-guix <at> gnu.org> wrote:
>> I can confirm the reproducibility issue.
>>
>> I have two x86_64-linux machines building guix to verify the fix, I'll apply
>> your patch once they produce matching outputs.
>
> Took me quite a while to build 5 rounds. :)
>
> --8<---------------cut here---------------start------------->8---
> $ guix hash --serializer=nar /gnu/store/fs7x07jfn7igpkwv3alrs9by21q70y13-guix-1.4.0-26.5ab3c4c
> 0kh87wb4qn97kwzrf4igal71cjvv143j6jr2y3dwfzcy1madj1ll
> --8<---------------cut here---------------end--------------->8---
>
> Applied #74112 as 4c56d0cccdc44e12484b26332715f54768738c5f, thanks!
Maybe I am missing something. To my knowledge, .go files produced by
Guile are not always reproducible, see bug#20272 [1]. And, from my
understanding, Guix cannot be reproducible until this bug had been
fixed. Therefore, I am not convinced that this patch is worth under
this frame considering the build-time penalty it brings.
That’s said, maybe it’s better than nothing and the package ’guix’ is
barely built after all. I do not know.
What people think?
Cheers,
simon
1: https://issues.guix.gnu.org/issue/20272
Information forwarded
to
bug-guix <at> gnu.org
:
bug#74204
; Package
guix
.
(Sun, 10 Nov 2024 09:13:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 74204-done <at> debbugs.gnu.org (full text, mbox):
Hi Simon,
Simon Tournier <zimon.toutoune <at> gmail.com> writes:
> Hi,
>
> On Tue, 05 Nov 2024 at 23:25, Hilton Chain via Bug reports for GNU Guix <bug-guix <at> gnu.org> wrote:
>
>>> I can confirm the reproducibility issue.
>>>
>>> I have two x86_64-linux machines building guix to verify the fix, I'll apply
>>> your patch once they produce matching outputs.
>>
>> Took me quite a while to build 5 rounds. :)
>>
>> --8<---------------cut here---------------start------------->8---
>> $ guix hash --serializer=nar /gnu/store/fs7x07jfn7igpkwv3alrs9by21q70y13-guix-1.4.0-26.5ab3c4c
>> 0kh87wb4qn97kwzrf4igal71cjvv143j6jr2y3dwfzcy1madj1ll
>> --8<---------------cut here---------------end--------------->8---
>>
>> Applied #74112 as 4c56d0cccdc44e12484b26332715f54768738c5f, thanks!
>
> Maybe I am missing something. To my knowledge, .go files produced by
> Guile are not always reproducible, see bug#20272 [1]. And, from my
> understanding, Guix cannot be reproducible until this bug had been
> fixed. Therefore, I am not convinced that this patch is worth under
> this frame considering the build-time penalty it brings.
>
> That’s said, maybe it’s better than nothing and the package ’guix’ is
> barely built after all. I do not know.
>
> What people think?
Perhaps we should set the default parallel-build? to #f in the
guile-build-system at least in the meantime, with a prominent comment as
to why and a reference to the upstream issue? Many Guile packages use
the gnu-build-system so that wouldn't cover all of them like
'guix'... I'm not sure.
It'd be nicer to fix the underlying guile issue (again?), but I doubt
many people are up to this.
--
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#74204
; Package
guix
.
(Thu, 14 Nov 2024 10:02:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 74204-done <at> debbugs.gnu.org (full text, mbox):
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
> Simon Tournier <zimon.toutoune <at> gmail.com> writes:
[...]
>> Maybe I am missing something. To my knowledge, .go files produced by
>> Guile are not always reproducible, see bug#20272 [1]. And, from my
>> understanding, Guix cannot be reproducible until this bug had been
>> fixed. Therefore, I am not convinced that this patch is worth under
>> this frame considering the build-time penalty it brings.
>>
>> That’s said, maybe it’s better than nothing and the package ’guix’ is
>> barely built after all. I do not know.
>>
>> What people think?
>
> Perhaps we should set the default parallel-build? to #f in the
> guile-build-system at least in the meantime, with a prominent comment as
> to why and a reference to the upstream issue? Many Guile packages use
> the gnu-build-system so that wouldn't cover all of them like
> 'guix'... I'm not sure.
Sounds good to me: packages using ‘guile-build-system’ are usually
relatively small so the impact is negligible.
‘guix’ is a little different because it takes so much time to build
sequentially…
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 12 Dec 2024 12:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 239 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.