| c026987fe3ef3f5d16f956176d4f52c464b46856 |
|
20-Aug-2015 |
Katherine Threlkeld <kathrelkeld@chromium.org> |
Improve logging for bluetooth_SDP_*AttributeRequest tests.
Add more logging statements and clarify error messages,
especially for the most frequent errors seen in the lab.
No functional changes to the behavior of the test.
ServiceSearchAttributeRequest:
- Split the giant and-ed line and make each sub-test fail instead of
returning False
- Add in the test name to failures
- Alter the current retry method to handle errors instead of bool
SDP tests:
- Split initial device reset into two sections which fail
independantly
- Set self.interactive before anything else, to avoid problems
if the later things fail
- Change output to hex instead of decimal where it makes sense
Client side code:
- Catch btsocket errors and timeouts and log more context info
- Add logging messages to low-level failures
- Check if adapter variable is None before using it
TEST=ran all bluetooth tests on a wificell and saw them pass
BUG=chromium:426260
Change-Id: I919524a984304334265a7e1658fee956fdfbfdb8
Reviewed-on: https://chromium-review.googlesource.com/294622
Reviewed-by: Mussa Kiroga <mussa@chromium.org>
Tested-by: Katherine Threlkeld <kathrelkeld@chromium.org>
Commit-Queue: Katherine Threlkeld <kathrelkeld@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| e686dcc4914aaf44164ce0cb9bd5dd243477fa76 |
|
06-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
bluetooth: test LE Discovery
BUG=chromium:439654
TEST=test_that $IP bluetooth_Sanity_LEDiscovery
Change-Id: I677fa9e3cd9bd12b5bde280152549db9adcb8ec8
Reviewed-on: https://chromium-review.googlesource.com/233721
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| f719e2d8dfc2610974c44186fac641cd215b7460 |
|
06-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
Bluetooth: add support for LE-only tester
BUG=chromium:439654
TEST=setup('peripheral') from test
Change-Id: I51040f850d0953777471b2155367adf41a0dd8ef
Reviewed-on: https://chromium-review.googlesource.com/233720
Reviewed-by: Michael Janssen <jamuraa@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| 071af2ec2c7712ec53a97640695451c52645aaf5 |
|
02-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
bluetooth_socket: expect reply to MGMT_OP_CONFIRM_NAME
On all our kernels, except 3.4, the kernel replies to this command now;
ignoring it was causing spurious debugging messages at bad times, so
deal with the reply properly.
BUG=none
TEST=test_that bluetooth_Sanity_Discovery
Change-Id: Ia9f91193f360b785bdbc689eccaa148c1597f00a
Reviewed-on: https://chromium-review.googlesource.com/232515
Tested-by: Scott James Remnant <keybuk@chromium.org>
Reviewed-by: Michael Janssen <jamuraa@chromium.org>
Reviewed-by: Arman Uguray <armansito@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| c7fd7a47c0ccb7da2bea83ba070e7350bf591c80 |
|
02-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
bluetooth_Sanity_DefaultState: handle BR/EDR whitelist
Recent kernels change the way they manage the "connectable" state of the
adapter. Instead of making the computer connectable to anything (which is
what this flag implies), instead the kernel uses the device whitelist to
determine what can connect.
The result is that the "connectable" flag remains off on systems running
3.10 or 3.14
Handle this in the autotest by checking whether the kernel supports the
"Add Device" management command and checking the opposite value of
"connectable" for those that do.
In addition, actually look at the raw HCI flags to check the PSCAN flag
and make sure that toggles on/off as we expect by adding and removing
a device.
BUG=chromium:433561
TEST=test_that bluetooth_Sanity_DefaultState
Change-Id: Ia43be23a8a1b0b5f7e14ae5aa8bd43fa2234e47e
Reviewed-on: https://chromium-review.googlesource.com/232514
Tested-by: Scott James Remnant <keybuk@chromium.org>
Reviewed-by: Michael Janssen <jamuraa@chromium.org>
Reviewed-by: Arman Uguray <armansito@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| abea37c34ea732b1c8c14cf3d4ecf5cf595c9f24 |
|
01-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
bluetooth_socket: add commands to add & remove device from action list
BUG=chromium:433561
TEST=test with an autotest
Change-Id: I110d2d1dd1a934f78de29de54c50cec79650821d
Reviewed-on: https://chromium-review.googlesource.com/232491
Tested-by: Scott James Remnant <keybuk@chromium.org>
Reviewed-by: Arman Uguray <armansito@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| 6556b7d1e9dc9f613cd97bf4ed92cac47aee8232 |
|
01-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
bluetooth_socket: sync to mgmt version 1.7
BUG=none
TEST=none
Change-Id: I423eb569697f36c83b11c26a4fc25e23ca2a223e
Reviewed-on: https://chromium-review.googlesource.com/232441
Reviewed-by: Arman Uguray <armansito@chromium.org>
Reviewed-by: Michael Janssen <jamuraa@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| f2fba24bb24ef2563d0e393c8c135c83fbc5977f |
|
01-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
bluetooth_socket: fix wrong controller index error
When making a command to the kernel, rather than the controller, e.g.
"version" or "read supported commands" we supply an index of 0xffff
and expect that in the response just as we expect 0x0 for the first
controller.
However the kernel may be reporting events for the controller itself
inbetween the command and the response, which will trip this error
check.
Move the error check inside the check for the command complete/status
events to fix that.
BUG=none
TEST=add a version check after a reset() call
Change-Id: I23eebceafbff8ef04dae29f79e475b13d0525c17
Reviewed-on: https://chromium-review.googlesource.com/232440
Reviewed-by: Arman Uguray <armansito@chromium.org>
Reviewed-by: Michael Janssen <jamuraa@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| 28c1eaf350f761d7e46a06ff2d6b7135bd3c096e |
|
08-Aug-2014 |
MengHuan Yu <menghuan@chromium.org> |
Fix a typo of set_fast_connectable() in BluetoothControlSocket
BUG=None
TEST=None
Change-Id: I75d2a8477895becdb6746738fd9df6219a3b3f34
Reviewed-on: https://chromium-review.googlesource.com/212899
Tested-by: MengHuan Yu <menghuan@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: MengHuan Yu <menghuan@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| da9f43cc5c84691d82b1dd9222fea37234cb9a0a |
|
08-Aug-2013 |
Scott James Remnant <keybuk@chromium.org> |
Bluetooth: implement bluetooth_Sanity_Discoverable
This test is the first example of a Bluetooth test with a separate
tester device (a stumpy with the testbed-ap profile is the intent).
It can be run two ways:
1. as bluetooth_Sanity_Discoverable - in which case the Tester will
be used to perform a device discovery and verify that the DUT
was detected in the process.
2. as bluetooth_Sanity_Discoverable.manual - in which case only the
DUT is used, and instructions presented on screen for use with
a third-party Tester (such as the Bluetooth PTS).
BUG=chromium:256771
TEST=run_remote_tests
Change-Id: I851a05acff3ca3edba32bb2f0cd043d8042d162d
Reviewed-on: https://gerrit.chromium.org/gerrit/65074
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|
| 1ca2e0e1b6cd0b6f5c2b972e44f3f63539d1dda6 |
|
01-Aug-2013 |
Scott James Remnant <keybuk@chromium.org> |
Bluetooth: implement first two Sanity checks
Check that the DUT has a Bluetooth adapter, and check that the Bluetooth
adapter address is not garbage.
BUG=chromium:256771
TEST=run_remote_tests
Change-Id: I0b87bf25ea103591c8eab2884e519a32c82f6c72
Reviewed-on: https://gerrit.chromium.org/gerrit/64003
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/client/common_lib/cros/bluetooth/bluetooth_socket.py
|