[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#28616] disable failing bluez test
From: |
Marius Bakke |
Subject: |
[bug#28616] disable failing bluez test |
Date: |
Tue, 03 Oct 2017 23:50:56 +0200 |
User-agent: |
Notmuch/0.25.1 (https://notmuchmail.org) Emacs/25.2.1 (x86_64-unknown-linux-gnu) |
Thomas Danckaert <address@hidden> writes:
> Thomas Danckaert <address@hidden> 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?
signature.asc
Description: PGP signature
- [bug#28616] disable failing bluez test, Thomas Danckaert, 2017/10/01
- [bug#28616] disable failing bluez test,
Marius Bakke <=
- [bug#28616] disable failing bluez test, Thomas Danckaert, 2017/10/04
- [bug#28616] disable failing bluez test, Marius Bakke, 2017/10/10
- [bug#28616] disable failing bluez test, Thomas Danckaert, 2017/10/11
- [bug#28616] disable failing bluez test, Thomas Danckaert, 2017/10/11
- [bug#28616] disable failing bluez test, Marius Bakke, 2017/10/11
- [bug#28616] disable failing bluez test, Thomas Danckaert, 2017/10/11
bug#28616: disable failing bluez test, Thomas Danckaert, 2017/10/07