From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 30299@debbugs.gnu.org
Subject: bug#30299: [core-updates] shepherd fails tests on all systems except x86_64
Date: Sun, 04 Feb 2018 23:48:29 +0100 [thread overview]
Message-ID: <87k1vsfk1u.fsf@gnu.org> (raw)
In-Reply-To: <87zi4uvi88.fsf@netris.org> (Mark H. Weaver's message of "Tue, 30 Jan 2018 22:07:35 -0500")
Hello,
Mark H Weaver <mhw@netris.org> skribis:
> On core-updates, Hydra has been unable to successfully build 'shepherd'
> on any system except x86_64-linux. I can also report that on my
> mips64el-linux GuixSD system, which is running something close to
> 'core-updates', I had to disable tests on shepherd in order to build it.
> I don't know about aarch64-linux.
>
> These are the tests that commonly fail:
>
> FAIL: tests/respawn.sh
> FAIL: tests/respawn-throttling.sh
> FAIL: tests/basic.sh
This is a non-deterministic failure. I could reproduce the
tests/basic.sh one and it is fixed by this:
https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=cc9564586729a5bb90dd5d2722b543fdde9ab821
I’ll roll a new Shepherd release soon and update the package.
The rest may be a duplicate of 23811, though I couldn’t reproduce it.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-02-04 22:49 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 [this message]
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
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=87k1vsfk1u.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30299@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).