** Changed in: python-dbusmock (Ubuntu)
Status: In Progress => Invalid
** Changed in: python-dbusmock (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Summary changed:
- FAIL: test_one_adapter (__main__.TestBlueZ5)
+ python-dbusmock: FAIL: test_one_adapter
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
Oh. Maybe this is a bluez regression. It looks like the shell code has
been rewritten and that's what is not working. Sometimes the test
commands from python-dbusmock don't get through.
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
