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

Issue 634054 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 635642
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

Device offline on chromium.perf: Android Nexus 5 Perf (1)

Project Member Reported by simonhatch@chromium.org, Aug 3 2016

Issue description

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

0d88c7fd25995e62: missing [logdog]
 
Labels: Type-Bug

Comment 2 by vhang@chromium.org, Aug 3 2016

Owner: vhang@chromium.org
Status: Assigned (was: Untriaged)
Can this wait until next week?  bpastene has a script that creates a bug with all the offline phones every monday and Hwops handles it.  If it can wait, then this bot will get fixed sometime next week.
Cc: sullivan@chromium.org
We're seeing lots of device issues (purple) on Nexus 5:

Android Nexus 5 Perf (1): https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29/builds/3861
Android Nexus 5 Perf (3): https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%283%29/builds/2766

Could someone look at them?

#2: +cc sullivan. No, I don't think this can wait. We need the bots to run benchmarks constantly to make sure that Chrome doesn't regress performance. Could the script run more often? Every day? Once an hour?
Cc: vhang@chromium.org
 Issue 634043  has been merged into this issue.
Ping? This host is still missing some devices:

https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29/builds/3912
Device 0a9c636f43e4b7c9 blacklisted
And https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%283%29/builds/2825:
Device 06b216a3f0e94e69 blacklisted
Device 03852c29003b9cb6 blacklisted

Comment 7 by vhang@chromium.org, Aug 9 2016

Cc: pschmidt@chromium.org
I'll take a look at this today when I get into the office unless pschmidt gets to it first.

Comment 8 by vhang@chromium.org, Aug 9 2016

I just check all 7 devices on build130-b1.  They all look ok to me.  

chrome-bot@build13-b1's password: 
List of devices attached 
0d88e86a43e4b0cc       device usb:2-1.2.2 product:hammerhead model:Nexus_5 device:hammerhead
0accace943e4af1c       device usb:2-1.2.4.2 product:hammerhead model:Nexus_5 device:hammerhead
0acbf65743e4b10a       device usb:2-1.2.4.1 product:hammerhead model:Nexus_5 device:hammerhead
0acc13b443e4b104       device usb:2-1.2.3 product:hammerhead model:Nexus_5 device:hammerhead
0d88c7fd25995e62       device usb:2-1.2.1 product:hammerhead model:Nexus_5 device:hammerhead
0d890b5f25995524       device usb:2-1.2.4.4 product:hammerhead model:Nexus_5 device:hammerhead
0a9c636f43e4b7c9       device usb:2-1.2.4.3 product:hammerhead model:Nexus_5 device:hammerhead

The latest 2 builds passed:

https://build.chromium.org/p/chromium.perf/buildslaves/build13-b1

Let me know if there's anything else I can do to help.
Mergedinto: 635642
Status: Duplicate (was: Assigned)
Sorry, I missed this.  Marking as a dup. as I took care of this via another bug.


Sign in to add a comment