Issue metadata
Sign in to add a comment
|
Device Offline Nexus 5 Perf (2) |
||||||||||||||||||||||
Issue descriptionhttps://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/2292 Traceback (most recent call last): File "/b/build/slave/Android_Nexus5_Perf__2_/build/src/build/android/buildbot/bb_device_status_check.py", line 241, in RecoverDevices reset_usb.reset_android_usb(serial) File "/b/build/slave/Android_Nexus5_Perf__2_/build/src/third_party/catapult/devil/devil/utils/reset_usb.py", line 48, in reset_android_usb 'Unable to determine bus or device for device %s' % serial) DeviceUnreachableError: Unable to determine bus or device for device 0748c4920059f1a7
,
Mar 11 2016
Still red, error the same: DeviceUnreachableError: Unable to determine bus or device for device 0748c4920059f1a7 Last green build: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/2245 (March 5th) First build that failed with the error we are currently seeing: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/2248 Only one CL for this build (https://codereview.chromium.org/1766923002) which is not relevant (Linux only), so this is almost certainly a hardware/infra issue.
,
Mar 11 2016
Temporarily relabeling Performance-Sheriff-BotHealth issues to Performance-BotHealth while we wait to migrate Performance-BotHealth issues to Performance-Sheriff-BotHealth.
,
Mar 14 2016
,
Apr 27 2016
,
Apr 27 2016
,
Apr 27 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vhang@google.com
, Mar 11 2016Status: Available (was: Untriaged)