New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 801396 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

bluetooth_qualification tests fail with new whirlwind image

Project Member Reported by rjahagir@chromium.org, Jan 12 2018

Issue description

I ran suite:bluetooth_qualification with the new whirlwind image that uses btsocket and got the following error: 


/tmp/test_that_results_ddmocr/results-4-bluetooth_SDP_ServiceAttributeRequest                                                     
FAIL: Unhandled Fault: <Fault 1: "<class 'autotest_lib.client.common_lib.cros.bluetooth.bluetooth_sdp_socket.BluetoothSDPSocketError'>:Error connecting to host: [Errno 112] Host is down">


Joseph, have you seen this issue before? I think it might be a servo or DUT issue. 

 
Kicked off with the following command on chromeos15-row1-rack9-host3: 

test_that -b peppy chromeos15-row1-rack9-host3 --args "tester=chromeos15-row1-rack9-host3-router" suite:bluetooth_qualification
Cc: briannorris@chromium.org
Labels: OS-Chrome
wouldn't you need at least the ".cros" subdomain, as in

--args "tester=chromeos15-row1-rack9-host3-router.cros"

?

Is that resolved on the server side, or on the DUT? (If the latter...then it probably won't resolve?)

At any rate, I saw the same problems.
The lack of the .cros subdomain is due to changes I made to my dhclient.conf file so this isn't the issue. 

The error still remains with bluetooth_sdp_socket. 

Comment 5 by mcchou@chromium.org, Apr 19 2018

Mergedinto: 716105
Status: Duplicate (was: Assigned)

Sign in to add a comment