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

Issue 685712 link

Starred by 0 users

Issue metadata

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



Sign in to add a comment

bot affinity 2 is broken on chromium.perf/Android Nexus9 Perf (2), affecting 10 tests

Project Member Reported by zh...@chromium.org, Jan 26 2017

Issue description

bot affinity 2 is broken on chromium.perf/Android Nexus9 Perf (2), affecting 10 tests

Type: infra-failure

Builders failed on: 
- Android Nexus9 Perf (2): 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus9%20Perf%20%282%29


HT4B7JT01059: adb status unauthorized [logdog]

 

Comment 1 by pschm...@google.com, Jan 26 2017

Owner: pschmidt@chromium.org
Status: Assigned (was: Available)
Status: Fixed (was: Assigned)
Device was stuck on the Google bootup splash screen.

Power cycled it and now it's back up.

chrome-bot@build12-b1:(Linux 14.04):~$ ./adb devices
List of devices attached
HT4B7JT01243	device
HT4B6JT02657	device
HT4B7JT01277	device
HT4B6JT02450	device
HT4B7JT01981	device
HT4B7JT01232	device
HT4B7JT01059	device

Effective starting with https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus9%20Perf%20%282%29/builds/4048

Sign in to add a comment