unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brice Waegeneire <brice@waegenei.re>
To: 30299@debbugs.gnu.org
Subject: bug#30299: [core-updates] shepherd fails tests on all systems except x86_64
Date: Thu, 19 Mar 2020 08:28:44 +0000	[thread overview]
Message-ID: <de75727fb11139381c68d8e3b55047ee@waegenei.re> (raw)
In-Reply-To: <87zi4uvi88.fsf@netris.org>

Hello,

Does this bug is still relevant?
It was reported on core-updates 2 years ago with shepherd 0.3.2.
I can't see any CI failures[0] related to a test failing since cuirass 
was setup, the only time the build of shepherd failed[1] it wasn't due 
to a test.
I wasn't able to reproduce the failing test with some building rounds on 
armhf and i686.

> I changed the severity to "serious", since this bug prevents installing
> GuixSD on arm, or creating an installation image. Also, it is now 
> present
> on master instead of core-updates.

As far as I know this isn't the case anymore, so at least the priority 
should be lowered.

[0]: http://ci.guix.gnu.org/search?query=shepherd
[1]: http://ci.guix.gnu.org/build/1312246/details

Brice.

  parent reply	other threads:[~2020-03-19  8:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  3:07 bug#30299: [core-updates] shepherd fails tests on all systems except x86_64 Mark H Weaver
2018-02-03 19:53 ` Efraim Flashner
2018-02-04 22:48 ` Ludovic Courtès
2018-02-14  8:52   ` Mark H Weaver
2018-02-14 13:00     ` Ludovic Courtès
2018-02-15 19:21     ` Mark H Weaver
2018-02-15 21:26       ` Ludovic Courtès
2018-02-17  0:04       ` Ludovic Courtès
2018-02-24 23:00         ` Andreas Enge
2018-02-14  9:16 ` Mark H Weaver
2020-03-19  8:28 ` Brice Waegeneire [this message]
2020-03-19  9:16   ` Marius Bakke
2020-03-20  9:58     ` bug#23811: shepherd: tests/respawn-throttling.sh fails sporadically Brice Waegeneire
2020-03-20 17:26       ` Marius Bakke

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=de75727fb11139381c68d8e3b55047ee@waegenei.re \
    --to=brice@waegenei.re \
    --cc=30299@debbugs.gnu.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).