Device offline on chromium.perf: Android Galaxy S5 Perf (3) |
||||
Issue descriptionLink to buildbot status page: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%283%29?numbuilds=200 Device "32082171745c5147" is offline / blacklisted: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%283%29/builds/2149/steps/device_status_check/logs/stdio E 9.166s Main Unable to reset USB for 32082171745c5147. Traceback (most recent call last): File "/b/build/slave/Android_Galaxy_S5_Perf__3_/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_Galaxy_S5_Perf__3_/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 32082171745c5147
,
Jun 1 2016
sheriff ping. still having 32082171745c5147: missing. And: Device 32089f2db2a351c5 blacklisted Device 32082171745c5147 blacklisted
,
Jun 1 2016
Issue 613130 has been merged into this issue.
,
Jun 2 2016
sheriff ping
,
Jun 2 2016
Device looked like it was powered off. It's back up now. No idea why 32089f2db2a351c5 is being blacklisted. It is responsive to adb commands and it passes the provisioning step. I went ahead and power cycled it anyway. Let's see what happens with the next build which will be https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%283%29/builds/2228 List of devices attached 3208d22daac2518f device 3208cd5005b25183 device 3208086b755c5135 device 32089f2db2a351c5 device 32089d0db6a351b7 device 3208e46a04b25131 device 32082171745c5147 device
,
Jun 3 2016
This looks good now. |
||||
►
Sign in to add a comment |
||||
Comment 1 by vhang@google.com
, May 26 2016Status: Available (was: Untriaged)