[Kernel-packages] [Bug 1750308] Re: FAIL: test_one_adapter (__main__.TestBlueZ5)
** 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 (__main__.TestBlueZ5)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1750308
Title:
python-dbusmock: FAIL: test_one_adapter (__main__.TestBlueZ5)
Status in Bluez Utilities:
Unknown
Status in bluez package in Ubuntu:
In Progress
Status in python-dbusmock package in Ubuntu:
Invalid
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1750308/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750308] Re: FAIL: test_one_adapter (__main__.TestBlueZ5)
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1750308
Title:
FAIL: test_one_adapter (__main__.TestBlueZ5)
Status in Bluez Utilities:
Unknown
Status in bluez package in Ubuntu:
In Progress
Status in python-dbusmock package in Ubuntu:
In Progress
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1750308/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750308] Re: FAIL: test_one_adapter (__main__.TestBlueZ5)
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)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: bluez (Ubuntu)
Importance: Undecided => Medium
** Changed in: bluez (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1750308
Title:
FAIL: test_one_adapter (__main__.TestBlueZ5)
Status in bluez package in Ubuntu:
In Progress
Status in python-dbusmock package in Ubuntu:
In Progress
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1750308/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
