From: Marius Bakke <mbakke@fastmail.com>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: 28616@debbugs.gnu.org
Subject: [bug#28616] disable failing bluez test
Date: Tue, 10 Oct 2017 23:40:39 +0200 [thread overview]
Message-ID: <877ew28yw8.fsf@fastmail.com> (raw)
In-Reply-To: <20171004.200454.31853833354551300.post@thomasdanckaert.be>
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
Thomas Danckaert <post@thomasdanckaert.be> writes:
> From: Marius Bakke <mbakke@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?
>
> 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>
Excerpt:
--8<---------------cut here---------------start------------->8---
CCLD unit/test-gatt
XPASS: unit/test-gatt
make --no-print-directory all-am
============================================================================
Testsuite summary for bluez 5.47
============================================================================
# TOTAL: 25
# PASS: 24
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 1
# ERROR: 0
============================================================================
See ./test-suite.log
============================================================================
make[3]: *** [Makefile:8597: test-suite.log] Error 1
make[2]: *** [Makefile:8705: check-TESTS] Error 2
make[1]: *** [Makefile:9089: check-am] Error 2
make: *** [Makefile:9091: check] Error 2
phase `check' failed after 331.2 seconds
--8<---------------cut here---------------end--------------->8---
XPASS is "unexpected pass" according to
<https://www.gnu.org/software/automake/manual/html_node/Generalities-about-Testing.html>.
I found the autotools documentation sparse on this, how do we make it
skip this test instead of expecting a failure?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-10-10 21:41 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
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 [this message]
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=877ew28yw8.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).