all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 26407-done@debbugs.gnu.org
Subject: bug#26407: test.dicod fails after ~20 hours of failed connection attempts
Date: Mon, 01 May 2017 23:15:13 +0200	[thread overview]
Message-ID: <878tmg1dpa.fsf@gnu.org> (raw)
In-Reply-To: <874lxyivup.fsf@netris.org> (Mark H. Weaver's message of "Sat, 08 Apr 2017 14:43:10 -0400")

Hi,

Mark H Weaver <mhw@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’.

      reply	other threads:[~2017-05-01 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-08 18:43 bug#26407: test.dicod fails after ~20 hours of failed connection attempts Mark H Weaver
2017-05-01 21:15 ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tmg1dpa.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26407-done@debbugs.gnu.org \
    --cc=mhw@netris.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.