python-dbusmock: FAIL: test_one_adapter (__main__.TestBlueZ5)

Bug #1750308 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bluez Utilities
Unknown
Unknown
bluez (Ubuntu)
Fix Released
Medium
Daniel van Vugt
python-dbusmock (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

When bluez 5.48 is installed, we see this failure:

======================================================================
FAIL: test_one_adapter (__main__.TestBlueZ5)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_bluez5.py", line 128, in test_one_adapter
    self.assertIn('Controller ' + address, out)
AssertionError: 'Controller 00:01:02:03:04:05' not found in ['Waiting to connect to bluetoothd...', '[\x1b[0;92mNEW\x1b[0m] Controller 00:01:02:03:04:05 my-computer [default]', '[SIGNAL] org.freedesktop.DBus.Mock.MethodCalled', 'Agent registered', 'Controller 00:01:02:03:04:05 my-computer [default]', 'Agent unregistered', '[\x1b[0;91mDEL\x1b[0m] Controller 00:01:02:03:04:05 my-computer [default]']

----------------------------------------------------------------------

However the failure only occurs in the Ubuntu package of python-dbusmock. It does not occur with the upstream git repo (run as 'tests/run-ubuntu-chroot').

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python-dbusmock 0.17-1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Mon Feb 19 11:42:48 2018
InstallationDate: Installed on 2017-12-12 (68 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
PackageArchitecture: all
SourcePackage: python-dbusmock
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in python-dbusmock (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
status: New → In Progress
importance: Undecided → Medium
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

Changed in bluez (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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

Changed in python-dbusmock (Ubuntu):
status: In Progress → Invalid
assignee: Daniel van Vugt (vanvugt) → nobody
summary: - FAIL: test_one_adapter (__main__.TestBlueZ5)
+ python-dbusmock: FAIL: test_one_adapter (__main__.TestBlueZ5)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in bluez (Ubuntu):
status: In Progress → Fix Committed
no longer affects: bluez
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluez - 5.48-0ubuntu3

---------------
bluez (5.48-0ubuntu3) bionic; urgency=medium

  * Add fix-lp1750308-upstream-commit-1bf03369.patch to fix command piping
    regression (mostly affecting python-dbusmock). (LP: #1750308)

 -- Daniel van Vugt <email address hidden> Wed, 21 Feb 2018 15:08:50 +0800

Changed in bluez (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.