This bug was fixed in the package python-dbusmock - 0.16.8-1
---
python-dbusmock (0.16.8-1) unstable; urgency=medium
* New upstream release:
- bluez5 template tests: Fix failure of test_no_adapters with BlueZ 5.45.
(LP: #1696480)
-- Martin Pitt Mon,
I released 0.16.8 upstream and uploaded it to Debian unstable, from
where it should autosync into Ubuntu devel soon.
** Changed in: python-dbusmock (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: python-dbusmock
Status: Fix Committed => Fix Released
--
You received this
Thanks Daniel! PR merged upstream. There are a few other test
deprecation warnings/failures I'm looking into before doing a release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696480
Title:
** Changed in: python-dbusmock
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696480
Title:
python3-dbusmock / test_no_adapters test fails with bluez
Upstream fix proposed:
https://github.com/martinpitt/python-
dbusmock/pull/29/commits/39ad4ac96ba55b05afa2919b87a4682c8994ee61
** Also affects: python-dbusmock
Importance: Undecided
Status: New
** Changed in: python-dbusmock
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
**
Bisected. The test failure started with bluez 5.45, and specifically in:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=6db3470c2ea161b4b808ad1fc80dfd7e014fd359
However this appears to be a feature and not a bug. So the actual bug is
just a poor test case in python3-dbusmock,
Interesting. The tests all passed in my local builds...
** Changed in: bluez (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696480
Title: