GNU bug report logs - #26407
test.dicod fails after ~20 hours of failed connection attempts

Previous Next

Package: guix;

Reported by: Mark H Weaver <mhw <at> netris.org>

Date: Sat, 8 Apr 2017 18:44:01 UTC

Severity: important

Done: ludo <at> gnu.org (Ludovic Courtès)

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: tracker <at> debbugs.gnu.org
Subject: bug#26407: closed (test.dicod fails after ~20 hours of failed
 connection attempts)
Date: Mon, 01 May 2017 21:16:01 +0000
[Message part 1 (text/plain, inline)]
Your message dated Mon, 01 May 2017 23:15:13 +0200
with message-id <878tmg1dpa.fsf <at> gnu.org>
and subject line Re: bug#26407: test.dicod fails after ~20 hours of failed connection attempts
has caused the debbugs.gnu.org bug report #26407,
regarding test.dicod fails after ~20 hours of failed connection attempts
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
26407: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26407
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Mark H Weaver <mhw <at> netris.org>
To: bug-guix <at> gnu.org
Subject: test.dicod fails after ~20 hours of failed connection attempts
Date: Sat, 08 Apr 2017 14:43:10 -0400
Recently, test.dicod has started failing after taking ~20 hours of
build-slot time, mostly filled with "Connection refused" errors:

  https://hydra.gnu.org/job/gnu/master/test.dicod.x86_64-linux

Here's a build that recently failed after 20 hours:

  https://hydra.gnu.org/build/1974589

and here's one that, as of the time of this writing, is currently 14
hours into the build, and stuck in the same "Connection refused" loop:

  https://hydra.gnu.org/build/1974709

      Mark


[Message part 3 (message/rfc822, inline)]
From: ludo <at> gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw <at> netris.org>
Cc: 26407-done <at> debbugs.gnu.org
Subject: Re: bug#26407: test.dicod fails after ~20 hours of failed connection
 attempts
Date: Mon, 01 May 2017 23:15:13 +0200
Hi,

Mark H Weaver <mhw <at> netris.org> skribis:

> Recently, test.dicod has started failing after taking ~20 hours of
> build-slot time, mostly filled with "Connection refused" errors:
>
>   https://hydra.gnu.org/job/gnu/master/test.dicod.x86_64-linux
>
> Here's a build that recently failed after 20 hours:
>
>   https://hydra.gnu.org/build/1974589
>
> and here's one that, as of the time of this writing, is currently 14
> hours into the build, and stuck in the same "Connection refused" loop:
>
>   https://hydra.gnu.org/build/1974709

I could reproduce the problem back when you reported it, but it seems
that it vanished (it works for me several times in raw):

  https://hydra.gnu.org/job/gnu/master/test.dicod.x86_64-linux

Previously, when it failed (as in
<https://hydra.gnu.org/build/1999217/nixlog/17/raw>, corresponding to
commit 1f49cd546ec350678e238353e8036f0792793901), the problem was:

  exec of "/gnu/store/mi5k7xi6wfhj2irdys7qc9fabpii60gh-dico-2.4/bin/dicod" failed: Permission denied

… and thus attempts to connect to dicod failed.

When I tried to debug it, this happened only when running dicod as user
“dicod”, and not when running it as root.  Also, this happened only when
running qemu non-interactively.

So I’m willing to punt on this one and disregard it as a qemu/kernel
issue.  Let’s reopen it if the problem comes back.

Thanks,
Ludo’.


This bug report was last modified 8 years and 27 days ago.

Previous Next


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