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, 03 Oct 2017 23:50:56 +0200 [thread overview]
Message-ID: <874lrfew8v.fsf@fastmail.com> (raw)
In-Reply-To: <87wp4f9oel.fsf@thomasdanckaert.be>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
Thomas Danckaert <post@thomasdanckaert.be> writes:
> Thomas Danckaert <post@thomasdanckaert.be> writes:
>
>> Now I checked properly, and the test still fails on this laptop. From
>> the thread I linked, I understand it's also a timing/time-out issue,
>> so perhaps the performance of the build host plays a role.
>
> On another (faster) machine, I also manage to build bluez. As the issue
> doesn't seem to affect many people (most use substitutes anyway), maybe
> we can keep the package as it this for now, and hope upstream improves
> the situation at some point (it's been reported, after all).
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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-10-03 21:52 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 [this message]
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=874lrfew8v.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).