From: Thomas Danckaert <post@thomasdanckaert.be>
To: mbakke@fastmail.com
Cc: 28616@debbugs.gnu.org
Subject: [bug#28616] disable failing bluez test
Date: Wed, 27 Sep 2017 22:59:11 +0200 (CEST) [thread overview]
Message-ID: <20170927.225911.2002293308035929753.post@thomasdanckaert.be> (raw)
In-Reply-To: <87h8vo9by2.fsf@fastmail.com>
From: Marius Bakke <mbakke@fastmail.com>
Subject: Re: [bug#28616] disable failing bluez test
Date: Wed, 27 Sep 2017 21:30:13 +0200
> 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.
>
> [...]
>
> Network is not available in the build container, so I wonder what's
> going on here.
Hmm, I now also get a substitute... Earlier I didn't get a
substitute and the build failed on my system, so I assumed the error
was general (but couldn't check the build status on hydra due to the
web frontend's unresponsiveness -- now it's available again).
I'll try to build it again a few times and will close this if i find
no more issues (or move the issue to guix bugs). Now it's getting
late (and I'm getting a hash mismatch for the pcre source from
sourceforge while trying to build bluez from source... I'm not going
down this rabbit hole tonight :-) ).
Thomas
next prev parent reply other threads:[~2017-09-27 21:00 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170927.225911.2002293308035929753.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=28616@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.