unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 33362@debbugs.gnu.org
Subject: bug#33362: System tests stuck in "shepherd[1]: waiting for udevd..."
Date: Fri, 26 Nov 2021 02:34:22 +0100	[thread overview]
Message-ID: <86o867r97l.fsf@gmail.com> (raw)
In-Reply-To: <871s7pu6k1.fsf@netris.org> (Mark H. Weaver's message of "Mon, 12 Nov 2018 20:09:07 -0500")

Hi Mark,

On Mon, 12 Nov 2018 at 20:09, Mark H Weaver <mhw@netris.org> wrote:

> As I write this, there are two system test builds that have been stuck
> for many hours, endlessly printing "shepherd[1]: waiting for udevd...":
>
>   https://hydra.gnu.org/build/3153725
>   https://hydra.gnu.org/build/3154365
>
> They are both on i686-linux, and on the 'core-updates' branch, but with
> two different build slaves (hydra.gnunet.org and guix.sjd.se).
>
> I will now abort these builds, to free up build slots for other jobs.

I am doing bug triage and I hit this old one #33362 [1] from 2018.  It
is about hydra which is down now, IIRC.  Does it still make sense to
keep it open?  Or can we close it?

1: <http://issues.guix.gnu.org/issue/33362>


Cheers,
simon




  parent reply	other threads:[~2021-11-26  1:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  1:09 bug#33362: System tests stuck in "shepherd[1]: waiting for udevd..." Mark H Weaver
2018-11-13 20:51 ` Mark H Weaver
2018-11-29 22:58   ` Mark H Weaver
2018-11-29 23:19     ` Danny Milosavljevic
2018-12-09  8:33     ` Mark H Weaver
2018-12-14 23:52   ` Mark H Weaver
2018-11-20 16:02 ` Ludovic Courtès
2018-12-09 21:46 ` Mark H Weaver
2021-11-26  1:34 ` zimoun [this message]
2021-11-26 23:21   ` Mark H Weaver
2022-01-04 23:21     ` zimoun
2022-02-03  2:37       ` zimoun

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=86o867r97l.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=33362@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).