From: Marius Bakke <mbakke@fastmail.com>
To: Thomas Danckaert <post@thomasdanckaert.be>, 28616@debbugs.gnu.org
Subject: [bug#28616] disable failing bluez test
Date: Wed, 27 Sep 2017 21:30:13 +0200 [thread overview]
Message-ID: <87h8vo9by2.fsf@fastmail.com> (raw)
In-Reply-To: <20170927.092105.443051876281349513.post@thomasdanckaert.be>
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
Thomas Danckaert <post@thomasdanckaert.be> writes:
> 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...
I can not reproduce this on GuixSD.
--8<---------------cut here---------------start------------->8---
PASS: unit/test-gobex-transfer
PASS: unit/test-avrcp CCLD unit/test-gatt
PASS: unit/test-gatt
make --no-print-directory all-am
============================================================================
Testsuite summary for bluez 5.47
============================================================================
# TOTAL: 25
# PASS: 25
--8<---------------cut here---------------end--------------->8---
Network is not available in the build container, so I wonder what's
going on here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-09-27 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 7:21 [bug#28616] disable failing bluez test Thomas Danckaert
2017-09-27 19:30 ` Marius Bakke [this message]
2017-09-27 20:59 ` Thomas Danckaert
2017-09-28 6:42 ` Thomas Danckaert
2017-10-01 10:02 ` Thomas Danckaert
2017-10-03 21:50 ` Marius Bakke
2017-10-04 18:04 ` Thomas Danckaert
2017-10-10 21:40 ` Marius Bakke
2017-10-11 6:52 ` Thomas Danckaert
2017-10-11 16:10 ` Thomas Danckaert
2017-10-11 16:23 ` Marius Bakke
2017-10-11 19:53 ` Thomas Danckaert
2017-10-07 19:53 ` bug#28616: " Thomas Danckaert
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=87h8vo9by2.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=28616@debbugs.gnu.org \
--cc=post@thomasdanckaert.be \
/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).