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

Issue 877153 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[Autotest failure] bluetooth_AdapterPairing.mouse.suspend_resume failing with different reasons

Project Member Reported by harpreet@chromium.org, Aug 23

Issue description

bluetooth_AdapterPairing.mouse.suspend_resume failing with different reasons


See the failure reason at the link below:
https://stainless.corp.google.com/search?view=list&first_date=2018-08-17&last_date=2018-08-23&suite=%5Ebluetooth%5C_chameleon%24&test=%5Ebluetooth_AdapterPairing%5C.mouse%5C.suspend_resume%24&status=FAIL&status=ERROR&status=ABORT&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false



Sample log...

08/21 15:53:42.705 INFO |bluetooth_adapter_:0374| [*** passed: test_device_is_paired]
08/21 15:53:48.330 ERROR|bluetooth_adapter_:0062| EnterCommandMode: <Fault 1: "<class 'chameleond.utils.bluetooth_rn42.RN42Exception'>:Failure to get advertised name in entering command mode: Unexpected response in getting advertised name: .">
08/21 15:53:48.330 ERROR|bluetooth_adapter_:0927| EnterCommandMode failed
08/21 15:53:48.331 ERROR|bluetooth_adapter_:0309| test_connection_by_device failed at the 1st time.
08/21 15:53:48.331 INFO |bluetooth_adapter_:0313| test_connection_by_device: retry the 2nd time.
08/21 15:53:49.349 INFO |bluetooth_adapter_:0280| retry: creating a new serial device...
08/21 15:53:49.349 INFO |bluetooth_adapter_:0195| Remove the old serial device and create a new one.
08/21 15:53:50.132 ERROR|bluetooth_adapter_:0062| EnterCommandMode: <Fault 1: "<class 'chameleond.utils.bluetooth_rn42.RN42Exception'>:Failure to get advertised name in entering command mode: Unexpected response in getting advertised name: .">
08/21 15:53:50.132 INFO |bluetooth_adapter_:0214| Skip rebooting chameleon.
08/21 15:53:50.132 ERROR|bluetooth_adapter_:0378| [--- failed: test_connection_by_device (None)]
08/21 15:53:55.172 INFO |bluetooth_adapter_:0374| [*** passed: test_device_name]
08/21 15:53:57.354 INFO |bluetooth_adapter_:0374| [*** passed: test_disconnection_by_adapter]
08/21 15:54:05.193 INFO |bluetooth_adapter_:0374| [*** passed: test_connection_by_device]
08/21 15:54:05.738 INFO |bluetooth_adapter_:0374| [*** passed: test_disconnection_by_device]
08/21 15:54:05.823 INFO |bluetooth_adapter_:0374| [*** passed: test_remove_pairing]
08/21 15:54:05.823 INFO |bluetooth_AdapterP:0182| ===  (pass = 0, fail = 1) / total 1  ===

08/21 15:54:05.823 DEBUG|              test:0381| Test failed due to {'Round 1': ['[--- failed: test_connection_by_device (None)]']}. Exception log follows the after_iteration_hooks.
 
Cc: shijinabraham@chromium.org
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment