This is another example where I think the device_recovery step is hammering things.

cat /b/c/b/Android_Release__Pixel_C_/src/out/bad_devices.json
{"5B24001812": {"timestamp": 1471542141.593427, "reason": "USB failure"}}

I rebooted the host, got into adb and the device seems to respond fine.

I've removed bad_devices.json 

It helped for now
https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%28Pixel%20C%29/builds/1022
I wonder why this bot can't survive running more than a couple of days.

Fails again

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome-golo/chrome-golo.git/+/c2a517586d84bc6f3767cfda13ef3d60cbdfd7d8

commit c2a517586d84bc6f3767cfda13ef3d60cbdfd7d8
Author: pschmidt <pschmidt@google.com>
Date: Mon Aug 22 21:03:05 2016

Closing this as it has been pretty stable for the last few weeks.