GNU bug report logs - #48389
Guile 3.0.7 test suite fails non-deterministically

Previous Next

To reply to this bug, email your comments to 48389 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Michael Jury <apple.link.level <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Guix pull failed
Date: Wed, 12 May 2021 17:51:01 -0600

[Message part 1 (text/plain, inline)]

guix pull: error: You found a bug: the program
'/gnu/store/0bgadpjvbbr1cs2pr9z4kqizx3k7smil-compute-guix-derivation'
failed to compute the derivation for Guix (version:
"6a724b0277f31245a0573c8347a6462786d7c0d1"; system: "x86_64-linux";
host version: "55aa50834fe07597adddbfc4e007de9420b195ec"; pull-version: 1).
Please report it by email to <bug-guix <at> gnu.org>.

Let me know if you want the backtrace or anything else

-- 
Best
-Michael Jury
"The question isn't who will let me, the question is who will stop me."

[Message part 2 (text/html, inline)]

Message #10 received at 48389 <at> debbugs.gnu.org (full text, mbox):

From: Michael Jury <apple.link.level <at> gmail.com>
To: 48389 <at> debbugs.gnu.org
Subject: Never mind.
Date: Thu, 13 May 2021 14:16:34 -0600

[Message part 1 (text/plain, inline)]

After a re-boot it went away.

I had tried pulling for a while assuming a network issue.
But didn't try a reboot.

[Message part 2 (text/html, inline)]

Message #19 received at 48389 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Leo Famulari <leo <at> famulari.name>
Cc: 48392 <at> debbugs.gnu.org, 48389 <at> debbugs.gnu.org
Subject: Re: bug#48389: Guix pull failed
Date: Thu, 13 May 2021 23:02:42 +0200

Hi,

Leo Famulari <leo <at> famulari.name> skribis:

> On Wed, May 12, 2021 at 09:34:15PM -0400, Leo Famulari wrote:
>> Guile 3.0.7 failed to build on the build farm, during the test suite.
>> 
>> There's nothing to link to on ci.guix.gnu.org because Cuirass can't
>> evaluate Guix without Guile.
>> 
>> I've attached the build log.
>
> I logged in to berlin.gnu.org and tried building the Guile derivation
> again. It failed once, then succeeded, then failed a few more times. So
> there is some nondeterminism in the test suite.

Ouch, apologies for that (I did test on all 4 platforms before pushing
and didn’t stumble upon this issue.)

The log you posted is mangled.  Do you have a clearer one at hand?

> At least now there is a substitute for it.

Yeah.

Thanks,
Ludo’.

Message #22 received at 48389 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 48392 <at> debbugs.gnu.org, 48389 <at> debbugs.gnu.org
Subject: Re: bug#48389: Guix pull failed
Date: Thu, 13 May 2021 21:26:22 -0400

[Message part 1 (text/plain, inline)]

On Thu, May 13, 2021 at 11:02:42PM +0200, Ludovic Courtès wrote:
> The log you posted is mangled.  Do you have a clearer one at hand?

I downloaded it from here, and it works:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48392#5

But now I've attached it uncompressed; it's only 281 KiB.

[k1n1d8zxni80jpxxgzjqrg5yzaj7sl-guile-3.0.7.drv (text/plain, attachment)]

Message #25 received at 48389 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Leo Famulari <leo <at> famulari.name>
Cc: 48392 <at> debbugs.gnu.org, 48389 <at> debbugs.gnu.org
Subject: Re: bug#48389: Guix pull failed
Date: Fri, 14 May 2021 11:44:18 +0200

Hi Leo,

Leo Famulari <leo <at> famulari.name> skribis:

> Running suspendable-ports.test
> UNRESOLVED: suspendable-ports.test: non-revealed port is closed
> ERROR: suspendable-ports.test: revealed port fdes not closed - arguments: ((system-error "seek" "~A" ("Bad file descriptor") (9)))

I can’t seem to reproduce it in the Guile build tree, neither with:

  while ./check-guile suspendable-ports.test ; do : ; done

nor with:

  while ./check-guile ; do : ; done

We’ll have to try to gather more info if it comes up again, or see if
there are configs that trigger it more easily.

Thanks,
Ludo’.

Message #28 received at 48389 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 48392 <at> debbugs.gnu.org, 48389 <at> debbugs.gnu.org
Subject: Re: bug#48389: Guix pull failed
Date: Mon, 7 Jun 2021 15:06:51 -0400

On Fri, May 14, 2021 at 11:44:18AM +0200, Ludovic Courtès wrote:
> We’ll have to try to gather more info if it comes up again, or see if
> there are configs that trigger it more easily.

It's happening again for the ungrafting evaluation:

https://ci.guix.gnu.org/eval/45377/log/raw (sorry, this log is unhelpful)
https://ci.guix.gnu.org/eval/45377

And Chris Baines sees it in the Guix Data Service too:

http://data.guix.gnu.org/gnu/store/djr1vmhnl8z8yy4ymkszw5srvfmfv943-guile-3.0.7.drv

For now I'm doing something like `guix gc --clear-failures
/gnu/store/...-guile-3.0.7 && guix build /gnu/store/...-guile-3.0.7.drv`
in a loop on the Berlin server.

Message #31 received at 48389 <at> debbugs.gnu.org (full text, mbox):

From: Carl Dong <contact <at> carldong.me>
To: 48389 <at> debbugs.gnu.org
Subject: Guile 3.0.7 test suite fails non-deterministically
Date: Thu, 15 Jul 2021 14:17:30 -0700

Hi all,

I’m also encountering this exact error when time-machining from 0961807915d7955e70a081272d857b6cbf92c0c8 to 83d9e2ee56cb0ca2a644074ad232503e25ac7116

I’m able to reproduce this (I’ve tried building the derivation 5 times now with different --cores, and this error happens every time)

Build logs here: https://nextcloud.carl.homeserver.net/s/yas2SwmST8Z3jRG
Keep-failed directory here: https://nextcloud.carl.homeserver.net/s/sSrjPZn5NqikeoJ

My system:
- AMD Ryzen Threadripper 2970WX 24-Core Processor
- Guix on Arch Linux
- tmpfs mounted on /tmp

Cheers,
Carl Dong
contact <at> carldong.me
"I fight for the users"

Message #34 received at 48389 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: 45788 <at> debbugs.gnu.org, 43521 <at> debbugs.gnu.org, 48389 <at> debbugs.gnu.org
Subject: ‘non-revealed port is
 closed’ test case is already fixed
Date: Mon, 19 Jul 2021 13:05:21 +0200

[Message part 1 (text/plain, inline)]

Hi guilers and guix,

I (and some other people) encountered this bug:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43521#11
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45788
https://issues.guix.gnu.org/48389#8

There is already a fix:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43521#11

Apparently it is already applied on Debian:

https://salsa.debian.org/rlb/deb-guile/-/commit/9fae58b134d8951e15b39b8e1751160a245228a6
https://salsa.debian.org/rlb/deb-guile/-/blob/f24ab0150132d906b9724128576c36c39361cab7/debian/patches/0007-Fix-non-revealed-port-is-closed-ports.test.patch

Maybe it can be applied now on 'main'? 

Also, could it be added to the 'patches' in Guix?

Greetings,
Maxime.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.