Guile 3 fails to build non-deterministically

  • Done
  • quality assurance status badge
Details
3 participants
  • Chris Marusich
  • Ludovic Courtès
  • Mathieu Othacehe
Owner
unassigned
Submitted by
Chris Marusich
Severity
important

Debbugs page

C
C
Chris Marusich wrote on 31 Dec 2020 11:16
(address . bug-guix@gnu.org)
87h7o123c7.fsf@gmail.com
Hi,

If you try to build Guile 3 without substitutes using any recent version
of Guix, it can frequently fail. I had to try about 12 times
in a row before it succeeded. The failure simply said "FAIL:
check-guile" - I didn't save the build logs, which were lost once the
build succeeded. If anyone is interested in debugging, it should be
easy to reproduce. Just do this:

- Run Guix in a 1-core VM or a similarly slow x86_64-linux system.

- Try to build any recent version of Guile 3 using any recent version of
Guix.

I've seen the failures happen for Guile 3.0.2 and Guile 3.0.4. I
observed this on a 1-core VM, so perhaps a slow system exacerbates this
bug. This can make running "guix pull" without substitutes tedious,
since you have to manually retry many times.

--
Chris
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAl/uI5kACgkQ3UCaFdgi
Rp3ZGxAAujwj4BsLc0ZGWH6hs3L7Lp0GNzyvNgFlfq8ey3TgBI4NwvdQsdzv5l/B
PWhz70M/EzA3h0Lv/jdvEHk2vRHweMqMG17a2KAqC6ODHhQ0qECuHoClMSAzho0+
8iuRlaziYeDdL2QLyA6T1gmuTgiz3z+Lbrg+pc7dxEcSGuoD50fZUoOWt7HxkEPX
+DN0x0jo1SnCQGs4jDcfGV2WoFiGKsIjSPJdAcgY5jNd2pn2FZ7La47x4vIoBE/H
OJR8Jb9D9eFNzkTmFL6gEVygVJuRTfzXTOcVNS3t7m4r2b8PLa409BpVf4AMmTzf
ilLyXGdMVGylfQpbs8PG/ncgQwqo064GWn0moYLejLF5GfnhsGwBZQ9Xi+cCD6nK
Hklw2zkXy+8LgM0Vvah2dEvimgHkgxCV4rGzGnejskezZ+/qJHc4CGsvE7I4xuIX
O3lNvtkvLkGcwsV/LpfbFjw1My1l9iymeMnaUu679UbgZZeNpxCnG9wpKkiT8rBb
7PBNg52FBzL0+hqzwdgEQjg/KoXXUPkbEdVrTsuxBBglh7LyO++AjVJxfnMB0INR
eL5XighXYK+JNH0LgaNM4D40/EcgR1/idzNZpn4yR93lJeqkzojoMethEpU+8LKn
M6unVg34Kf/lDuraBogJmMQtHgzg2dYQX+HV1IJnGv4+fRcdLhI=
=Kea/
-----END PGP SIGNATURE-----

M
M
Mathieu Othacehe wrote on 12 Jan 2021 02:38
(name . Chris Marusich)(address . cmmarusich@gmail.com)(address . 45574@debbugs.gnu.org)
874kjmtp85.fsf@gnu.org
Hello Chris,

Toggle quote (7 lines)
> If you try to build Guile 3 without substitutes using any recent version
> of Guix, it can frequently fail. I had to try about 12 times
> in a row before it succeeded. The failure simply said "FAIL:
> check-guile" - I didn't save the build logs, which were lost once the
> build succeeded. If anyone is interested in debugging, it should be
> easy to reproduce. Just do this:

I investigated those failures yesterday. I think they are caused by:

Let's see if the fix proposed by Rob can be merged in Guile.

Thanks,

Mathieu
L
L
Ludovic Courtès wrote on 8 Feb 2021 13:28
control message for bug #45574
(address . control@debbugs.gnu.org)
87czxaxn8p.fsf@gnu.org
severity 45574 important
quit
L
L
Ludovic Courtès wrote on 6 Sep 00:20 -0700
Re: bug#45574: Guile 3 fails to build non-deterministically
(address . 45574-done@debbugs.gnu.org)
87a5gl45a1.fsf@gnu.org
Chris Marusich <cmmarusich@gmail.com> skribis:

Toggle quote (17 lines)
> If you try to build Guile 3 without substitutes using any recent version
> of Guix, it can frequently fail. I had to try about 12 times
> in a row before it succeeded. The failure simply said "FAIL:
> check-guile" - I didn't save the build logs, which were lost once the
> build succeeded. If anyone is interested in debugging, it should be
> easy to reproduce. Just do this:
>
> - Run Guix in a 1-core VM or a similarly slow x86_64-linux system.
>
> - Try to build any recent version of Guile 3 using any recent version of
> Guix.
>
> I've seen the failures happen for Guile 3.0.2 and Guile 3.0.4. I
> observed this on a 1-core VM, so perhaps a slow system exacerbates this
> bug. This can make running "guix pull" without substitutes tedious,
> since you have to manually retry many times.

I don’t think that applies to 3.0.9, or at least I haven’t seen any such
failures or reports thereof. Closing!

Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 45574@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 45574
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch