New issue
Advanced search Search tips

Issue 736468 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

possible bad Nexus5 device

Project Member Reported by martiniss@chromium.org, Jun 23 2017

Issue description

Builders failed on: 
- Android Nexus5 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf


It looks like a device is failing? If you look at https://chromium-swarm.appspot.com/bot?id=build13-b1--device6&sort_stats=total%3Adesc, it has a bunch of failures. Most of the failures look like they can't reach the device.

https://viceroy.corp.google.com/chrome_infra/Machines/per_android_device?device_id=0d890b5f25995524&duration=1d&refresh=-1 doesn't look super suspicious to me.

Ben or John, any ideas?
 
Components: Infra>Labs
Wonder if this is some problem with the USB in the lab
Looking through the logs on the bot, there seems to be nothing obviously wrong with the device. Might just need a reflash or replacement.
Owner: vhang@chromium.org
Status: Assigned (was: Available)
Vince, could we replace that device? It's serial number 0d890b5f25995524 on build13-b1. It looks like it's been offline for 40 minutes, according to swarming.

Comment 4 by jo...@google.com, Jun 23 2017

Owner: jo...@chromium.org

Comment 5 by jo...@chromium.org, Jun 23 2017

Flashed up a replacement. Letting it charge a bit on AC before attaching.

Thanks.

Comment 6 by jo...@chromium.org, Jun 23 2017

Status: Fixed (was: Assigned)
0d890b5f25995524 -> 01ab57d7032fd01a
Status: Available (was: Fixed)
The new device is acting up. It's constantly disconnecting/reconnecting to the host:

chrome-bot@build13-b1:(Linux 14.04):~$ sudo grep "01ab57d7032fd01a" /var/log/syslog | tail
Jun 26 12:48:59 build13-b1 kernel: [69882.614226] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:50:13 build13-b1 kernel: [69955.971575] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:51:31 build13-b1 kernel: [70034.313383] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:51:31 build13-b1 kernel: [70034.696624] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:52:36 build13-b1 kernel: [70098.980302] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:53:40 build13-b1 kernel: [70162.752938] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:53:40 build13-b1 kernel: [70163.263987] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:53:51 build13-b1 kernel: [70173.743274] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:54:45 build13-b1 kernel: [70227.547265] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a
Jun 26 12:54:46 build13-b1 kernel: [70229.207900] usb 1-4.4.3: SerialNumber: 01ab57d7032fd01a

Maybe the hub or usb cable is bad?

Comment 8 by jo...@google.com, Jun 26 2017

Ack. We'll replace both, just to be sure.

Comment 9 by jo...@chromium.org, Jun 26 2017

Status: Fixed (was: Available)
hub/cables have been replaced. 

List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0a9c636f43e4b7c9	device
03ab1826003b9ed7	device
0acc13b443e4b104	device
06c10127003ba4f4	device
01ab57d7032fd01a	device
0acbf65743e4b10a	device
0d88e86a43e4b0cc	device

Fixing, but feel free to un-fix if anything else is required. Thanks.

Tentatively looking better now; thanks John!

Sign in to add a comment