[Autotest Failure] bluetooth_AdapterLEAdvertising.multiple failing with different reasons |
|||
Issue descriptionbluetooth_AdapterLEAdvertising.multiple test is failing with different reasons failure link below : https://stainless.corp.google.com/search?exclude_retried=true&first_date=2018-08-17&master_builder_name=&builder_name_number=&shard=&exclude_acts=true&builder_name=&master_builder_name_number=&owner=&retry=&exclude_cts=true&exclude_non_production=false&hostname=&board=&test=%5Ebluetooth_AdapterLEAdvertising%5C.multiple%24&suite=bluetooth_qualification%7Cbluetooth_chameleon%7Cbluetooth_sanity%7Cbluetooth_stress&build=%5ER70%5C-10991%5C.0%5C.0%24&status=FAIL&status=ERROR&status=ABORT&reason=&waterfall=&exclude_not_run=false&last_date=2018-08-23&exclude_non_release=true&exclude_au=true&model=&view=list
,
Oct 9
,
Jan 4
One failure is
failed: test_reset_advertising ({'advertising_disabled': True, 'reset_advertising_intervals': False, 'advertisement_removed': True})]
The test is expecting the string "“ Reset Advertising Intervals” in btmon logs. On some devices btmon fails to print this string "= bluetoothd: Set Advertising Intervals: 0x0140, 0x0140" and this failure occurs.
,
Jan 7
“Reset Advertising Intervals” is not being printed to btmon logs because sendmsg is failing in https://chromium.googlesource.com/chromiumos/third_party/bluez/+/release-R72-11316.B/src/log.c#125 causing logging_fd to closed thereby causing btd_info to not call logging_log. |
|||
►
Sign in to add a comment |
|||
Comment 1 by pbath...@chromium.org
, Aug 24