OK. I have tracked down the regression to bluez, with a simple test case. However since the bug doesn't affect normal user operation of bluez, we don't really need to wait for a bluez fix. We could work around it in python-dbusmock if necessary. Or even ignore the failing test.
It may turn out to be a matter of opinion as to whether this is a bug in bluez at all, or if python-dbusmock was always using it wrong... https://bugzilla.kernel.org/show_bug.cgi?id=198819 ** Bug watch added: Linux Kernel Bug Tracker #198819 https://bugzilla.kernel.org/show_bug.cgi?id=198819 ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=198819 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750308 Title: FAIL: test_one_adapter (__main__.TestBlueZ5) To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1750308/+subscriptions -- ubuntu-bugs mailing list firstname.lastname@example.org https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs