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

Issue 593536 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

adb_host.is_up flake after device is rebooted

Project Member Reported by dshi@chromium.org, Mar 10 2016

Issue description

It seems that adb get-state could be flake after a device is reboot. Attached log is the get-state output for every second after a device is rebooted.

You can see that the value is very flake after the device is first up and starts showing value "device". The problem is that, after the device is considered to be up, that is, get-state reads as device, autotest will try to run test through adb command. The flake may lead to adb command failure.

Will it be reasonable to force checking adb get-state for at least 10 or 30s. The device is only considered to be up after all checks return "device". We can force the logic only for checks after the dut is rebooted.

 
get-state.txt
10.9 KB View Download

Comment 1 by krisr@chromium.org, Mar 10 2016

I think that is ok, also can you use:
  $ adb wait-for-X

to verify it is in the state you want?

Comment 2 by autumn@chromium.org, Mar 14 2016

Owner: dshi@chromium.org
Status: Started (was: Untriaged)

Comment 3 by benhenry@google.com, Apr 26 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS

Comment 4 by dshi@chromium.org, Jul 19 2016

Status: WontFix (was: Started)
The flake doesn't cause issue now.

Sign in to add a comment