From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/03: gnu: bluez: Work around test failure on ARM.
Date: Sat, 05 Aug 2017 18:51:04 -0400 [thread overview]
Message-ID: <87efsp4oiv.fsf@netris.org> (raw)
In-Reply-To: <20170804223445.715A420660@vcs0.savannah.gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22's\?\= message of "Fri, 4 Aug 2017 18:34:45 -0400 (EDT)")
ludo@gnu.org (Ludovic Courtès) writes:
> civodul pushed a commit to branch core-updates
> in repository guix.
>
> commit 90ea83ee95ad467fc4a49f4c42d0df94d2952330
> Author: Ludovic Courtès <ludo@gnu.org>
> Date: Sat Aug 5 00:02:55 2017 +0200
>
> gnu: bluez: Work around test failure on ARM.
>
> This aims to skip the segfaulting test at
> <https://hydra.gnu.org/build/2195551>.
I also noticed that a great many failures on ARM are due to a bluez
failure, but this seems to be a case where Hydra is misbehaving again.
The bluez build on ARM, as found by searching for "bluez" in the
evaluation, actually succeeded:
https://hydra.gnu.org/build/2185022
However, this is not the same bluez derivation that Hydra is using as
inputs to many other packages. Looking at the source code, I see only
one bluez package. This reminds me of similar problems I had on
'core-updates' some time ago, when I resorted to making a new
'core-updates-2' jobset to work around this problem.
Any idea what's going on here?
Mark
parent reply other threads:[~2017-08-05 22:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170804223445.715A420660@vcs0.savannah.gnu.org>]
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=87efsp4oiv.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).