unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Re: 01/03: gnu: bluez: Work around test failure on ARM.
       [not found] ` <20170804223445.715A420660@vcs0.savannah.gnu.org>
@ 2017-08-05 22:51   ` Mark H Weaver
  0 siblings, 0 replies; only message in thread
From: Mark H Weaver @ 2017-08-05 22:51 UTC (permalink / raw)
  To: Ludovic Courtès; +Cc: guix-devel

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2017-08-05 22:51 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20170804223444.21093.66928@vcs0.savannah.gnu.org>
     [not found] ` <20170804223445.715A420660@vcs0.savannah.gnu.org>
2017-08-05 22:51   ` 01/03: gnu: bluez: Work around test failure on ARM Mark H Weaver

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).