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

Issue 629532 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

Device offline on chromium.perf - Android Nexus 5 (2)

Project Member Reported by eakuefner@chromium.org, Jul 19 2016

Issue description

Link to buildbot status page: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/3389

The offline device is 0acc190243e4b04c
 
Owner: pschmidt@chromium.org
Status: Fixed (was: Untriaged)
Device was up and responsive.  Soft rebooted it and now it's adb aware.

List of devices attached
0d88db4443e4b0d5	device
0d88d39743e4b8df	device
0acc190243e4b04c	device
0acca27c25995770	device
01ab21250c33f25f	device
0748c4920059f1a7	device
0accf87325995bd0	device
Status: Assigned (was: Fixed)
Re-opening: device is offline in the most recent build: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/3408

Comment 3 by jo...@google.com, Jul 20 2016

Power-cycled and swapped out the USB cable this time as well.

List of devices attached 
0d88db4443e4b0d5	device
0748c4920059f1a7	device
0accf87325995bd0	device
0acca27c25995770	device
0acc190243e4b04c	device
01ab21250c33f25f	device
0d88d39743e4b8df	device

Comment 4 by eyaich@chromium.org, Jul 22 2016

 Issue 630613  has been merged into this issue.
Status: Started (was: Assigned)
Just replaced 0acc190243e4b04c with 049976abf0c9eee3

If this replacement still drops offline then replacing the hub is next.

Effective starting with the next build which will be https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/3423

Comment 7 by picksi@chromium.org, Jul 25 2016

Some purpleness on the 22nd, but entirely red otherwise.

One recent failure's log file says: 

@@@STEP_LOG_LINE@json.output@  "_host_info": {@@@
@@@STEP_LOG_LINE@json.output@    "devices": {@@@
@@@STEP_LOG_LINE@json.output@      "build_types": "userdebug/dev-keys", @@@
@@@STEP_LOG_LINE@json.output@      "build_versions": "MISMATCH", @@@
@@@STEP_LOG_LINE@json.output@      "build_versions_list": [@@@
@@@STEP_LOG_LINE@json.output@        "4.4.2/KOT49H/937116", @@@
@@@STEP_LOG_LINE@json.output@        "4.4.4/KTU84P/1227136"@@@


Not sure if the 'MISMATCH'is indicative of a real issue?
Yes, that's a real issue! Different versions of K are installed on the devices! They should all have KOT49H. pschmidt, can you take a look?

Comment 9 by pschm...@google.com, Jul 25 2016

My bad.  Sorry about that.  Just fixed it.

Checking 0d88db4443e4b0d5...
hammerhead-userdebug 4.4.2 KOT49H 937116 dev-keys
Checking 0accf87325995bd0...
hammerhead-userdebug 4.4.2 KOT49H 937116 dev-keys
Checking 01ab21250c33f25f...
hammerhead-userdebug 4.4.2 KOT49H 937116 dev-keys
Checking 0d88d39743e4b8df...
hammerhead-userdebug 4.4.2 KOT49H 937116 dev-keys
Checking 049976abf0c9eee3...
hammerhead-userdebug 4.4.2 KOT49H 937116 dev-keys
Checking 0acca27c25995770...
hammerhead-userdebug 4.4.2 KOT49H 937116 dev-keys
Checking 0748c4920059f1a7...
hammerhead-userdebug 4.4.2 KOT49H 937116 dev-keys
Labels: Type-Bug
Status: Fixed (was: Started)
This looks stable now.  Closing.

Sign in to add a comment