GNU bug report logs -
#48405
Test suite failures on IPv6 only machines
Previous Next
To reply to this bug, email your comments to 48405 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#48405
; Package
guix
.
(Thu, 13 May 2021 20:52:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Vagrant Cascadian <vagrant <at> debian.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Thu, 13 May 2021 20:52:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
When building guix on Debian's buildd infrastructure, some of the test
suites fail when building on machines that only have IPv6:
https://buildd.debian.org/status/logs.php?pkg=guix&arch=amd64
In this case, the machine "x86-conova-01" is the only one that
fails to build, and one of the main differences from other machines may
be that it is IPv6 only.
The specific build logs for the failures appear here:
https://buildd.debian.org/status/fetch.php?pkg=guix&arch=amd64&ver=1.3.0-1&stamp=1620886911&raw=0
https://buildd.debian.org/status/fetch.php?pkg=guix&arch=amd64&ver=1.2.0-1&stamp=1606172126&raw=0
https://buildd.debian.org/status/fetch.php?pkg=guix&arch=amd64&ver=1.2.0%7Erc2-1&stamp=1605882853&raw=0
This may be related to use of AI_ADDRCONFIG with getaddrinfo:
https://lists.debian.org/debian-devel/2020/07/msg00070.html
I haven't yet figured out how to reproduce an environment in which this
fails consistently; maybe reproducing it in a guix container would be
possible?
live well,
vagrant
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 4 years and 30 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.