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: 33362@debbugs.gnu.org
Subject: bug#33362: System tests stuck in "shepherd[1]: waiting for udevd..."
Date: Tue, 20 Nov 2018 17:02:59 +0100	[thread overview]
Message-ID: <87zhu3ybws.fsf@gnu.org> (raw)
In-Reply-To: <871s7pu6k1.fsf@netris.org> (Mark H. Weaver's message of "Mon, 12 Nov 2018 20:09:07 -0500")

Hi Mark,

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

> As I write this, there are two system test builds that have been stuck
> for many hours, endlessly printing "shepherd[1]: waiting for udevd...":

Basic system tests pass for me on current-ish ‘core-updates’, on x86_64:

--8<---------------cut here---------------start------------->8---
$ git describe
v0.15.0-4036-g2d546858b1
$ make check-system TESTS='basic openssh mcron'
Compiling Scheme modules...
Running 3 system tests...
TOTAL: 3
PASS: /gnu/store/3zywc7y192p0n8l2cbm58vdkbpi3dchw-basic
PASS: /gnu/store/sirffl42jh6as45fy98frdfaglkgqif0-mcron
PASS: /gnu/store/pdw9jxq745w4833jx4hzfma6c48kwda8-openssh
--8<---------------cut here---------------end--------------->8---

Does the problem still show up for you?

Ludo’.

  parent reply	other threads:[~2018-11-20 16:04 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 [this message]
2018-12-09 21:46 ` Mark H Weaver
2021-11-26  1:34 ` zimoun
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

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

  git send-email \
    --in-reply-to=87zhu3ybws.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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 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.