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, expecting the bluetoothctl
log to always be silent other than a very specific message. That's just
not true in BlueZ 5.45 and it's not a bug...
** Changed in: bluez (Ubuntu)
Status: In Progress => Invalid
** Also affects: python-dbusmock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-dbusmock (Ubuntu)
Importance: Undecided => Medium
** Changed in: python-dbusmock (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: python-dbusmock (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:
python3-dbusmock / test_no_adapters test fails with bluez 5.45
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1696480/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
