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


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Thomas Danckaert <post <at> thomasdanckaert.be>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#28616: closed (disable failing bluez test)
Date: Sat, 07 Oct 2017 19:54:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Sat, 07 Oct 2017 21:53:32 +0200 (CEST)
with message-id <20171007.215332.1638924873548511082.post <at> thomasdanckaert.be>
and subject line Re: [bug#28616] disable failing bluez test
has caused the debbugs.gnu.org bug report #28616,
regarding disable failing bluez test
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
28616: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=28616
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Thomas Danckaert <post <at> thomasdanckaert.be>
To: guix-patches <at> gnu.org
Subject: disable failing bluez test
Date: Wed, 27 Sep 2017 09:21:05 +0200 (CEST)
[Message part 3 (text/plain, inline)]
A test for the bluez package that previously failed only (?) on ARM, 
now seems to fail more widely.

It seems the same problem was discussed on the linux-bluetooth 
mailing list here. https://marc.info/?t=149578476300002&r=1&w=2  
Apparently the test fails when no network is available.

I suggest to disable the test for now...

Thomas
[0001-gnu-bluez-Mark-segfaulting-test-with-XFAIL.patch (text/x-patch, inline)]
From 6a1a2c0e437552109be72ff257fbd9ae410774c1 Mon Sep 17 00:00:00 2001
From: Thomas Danckaert <post <at> thomasdanckaert.be>
Date: Wed, 27 Sep 2017 09:14:02 +0200
Subject: [PATCH] gnu: bluez: Mark segfaulting test with XFAIL.

 * gnu/packages/linux.scm (bluez): [arguments] Mark test-gatt with XFAIL.
---
 gnu/packages/linux.scm | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index 2a3a40801..a50e465f1 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -3090,10 +3090,9 @@ Bluetooth audio output devices like headphones or loudspeakers.")
                   (string-append (assoc-ref inputs "eudev") "/bin/udevadm")))
                #t))))
 
-       ;; FIXME: Skip one test that segfaults on ARM.
-       ,@(if (string=? (%current-system) "armhf-linux")
-             '(#:make-flags '("XFAIL_TESTS=unit/test-gatt"))
-             '())))
+       ;; FIXME: Skip one test that segfaults.
+       #:make-flags '("XFAIL_TESTS=unit/test-gatt")))
+
     (native-inputs
      `(("pkg-config" ,pkg-config)
        ("gettext" ,gettext-minimal)))
-- 
2.14.1

[Message part 5 (message/rfc822, inline)]
From: Thomas Danckaert <post <at> thomasdanckaert.be>
To: mbakke <at> fastmail.com, 28616-done <at> debbugs.gnu.org
Subject: Re: [bug#28616] disable failing bluez test
Date: Sat, 07 Oct 2017 21:53:32 +0200 (CEST)
From: Marius Bakke <mbakke <at> fastmail.com>
Subject: Re: [bug#28616] disable failing bluez test
Date: Tue, 03 Oct 2017 23:50:56 +0200

> I think we should apply the patch regardless (on 'core-updates'), with a
> link to the upstream discussion.  IMO it's more important to be able to
> build from source regardless of hardware, than running this one unit
> test.  What do you think?

done!

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.