GNU bug report logs - #28616
disable failing bluez test

Previous Next

Package: guix-patches;

Reported by: Thomas Danckaert <post <at> thomasdanckaert.be>

Date: Wed, 27 Sep 2017 07:22:02 UTC

Severity: normal

Done: Thomas Danckaert <post <at> thomasdanckaert.be>

Bug is archived. No further changes may be made.

Full log


Message #34 received at 28616 <at> debbugs.gnu.org (full text, mbox):

From: Thomas Danckaert <post <at> thomasdanckaert.be>
To: mbakke <at> fastmail.com
Cc: 28616 <at> debbugs.gnu.org
Subject: Re: [bug#28616] disable failing bluez test
Date: Wed, 11 Oct 2017 08:52:12 +0200 (CEST)
From: Marius Bakke <mbakke <at> fastmail.com>
Subject: Re: [bug#28616] disable failing bluez test
Date: Tue, 10 Oct 2017 23:40:39 +0200

>> I agree.
>>
>> I'll push this to core-updates then.
>
> On second thought, "bluez" is currently failing on armhf, seemingly 
> due
> to the original patch: 
> <https://hydra.gnu.org/build/2304811/nixlog/4/raw>
>
> [...]
>
> I found the autotools documentation sparse on this, how do we make 
> it
> skip this test instead of expecting a failure?

How annoying :-)  I couldn't find a way either.  What we can do is 
pass all 24 other tests as a make TESTS="..." flag..., or modify the 
'test-gatt' file itself so it returns '77', which is SKIP (we could 
use substitute* to insert a “return 77;” in main()).  Neither is very 
elegant...

Thomas

This bug report was last modified 7 years and 225 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.