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

Issue 903576 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[Autotest] bluetooth_AdapterPairing.mouse fails with ["[--- failed: test_stop_discovery ({'stop_discovery': False, 'is_not_discovering': False})]

Project Member Reported by shijinabraham@chromium.org, Nov 8

Issue description

 
Chrome OS: R71-11077

What steps will reproduce the problem?
Run bluetooth_AadpterPairing test. (I was able to recreate this failure on sabin. )

What is the expected result?
Test passes

What happens instead?
test_stop_discovery fails with 
["[--- failed: test_stop_discovery ({'stop_discovery': False, 'is_not_discovering': False})]

The failure seems to have started in R70-10991






 
Status: Started (was: Untriaged)
It seems like is_discovering() return True for around 60+ seconds after stop_discovery is called. Setting ADAPTER_WAIT_DEFAULT_TIMEOUT_SECS to a higher  value (90 seconds) will fix the test.
This test fails with the following error on some devices

10:40:44 INFO | autoserv| test_device_class_of_service: <Fault 1: "<type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0x98 in position 3: invalid start byte">

This is due to "EIR" key containing some value that cannot be encoded using utf-8.

dbus.Dictionary({dbus.String(u'EIR'): dbus.ByteArray('\n\tRNBT-61B9\x04\r\x80\x05\x00'


Submited https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1331166 to increase the timeout after stop_discovery.

@josephsih, What is the expected time for is_discovering to fail after stop_discovery is called? I have seen it take ~60 seconds on Sabin.

Sign in to add a comment