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

Issue 595696 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Device offline on chromium.perf Android Nexus5 Perf (2)

Project Member Reported by petrcermak@chromium.org, Mar 17 2016

Issue description

Link to buildbot status page: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/2354

All steps with device affinity 0 are failing.

I suspect it has something to do with the fact that, according to the device_status_check step (https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/2354/steps/device_status_check/logs/stdio), there's an "(error)" device:

I    0.047s Main  Expected devices:
I    0.047s Main    (error)
I    0.047s Main    0acc190243e4b04c
I    0.047s Main    0d88db4443e4b0d5
I    0.047s Main    0acca27c25995770
I    0.047s Main    0d88d39743e4b8df
I    0.047s Main    0748c4920059f1a7
I    0.047s Main    01ab21250c33f25f
I    0.047s Main    0accf87325995bd0

 

Comment 1 by pschm...@google.com, Mar 17 2016

Owner: pschmidt@chromium.org
Status: Started (was: Untriaged)
Fixed up:
/b/build/site_config/.known_devices
/b/build/slave/Android_Nexus5_Perf__2_/build/src/out/.last_devices
/b/build/slave/Android_Nexus5_Perf__2_/build/src/out/bad_devices.json

Will monitor next build.
Status: Fixed (was: Started)
The next few builds showed no change.  Then replaced the hub and since https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/2358 things look fine.

Closing.

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

Components: Infra>Labs
Labels: -Infra-Labs

Sign in to add a comment