build3-b3 has no devices attached. |
|||
Issue descriptionFull logs: https://build.chromium.org/p/client.webrtc.perf/builders/Android32%20Tests%20%28N%20Nexus6%29/builds/3463/steps/provision_devices/logs/stdio E 0.012s Main No available devices to provision. E 0.013s Main Local device blacklist: {u'ZY222X5LBG': {u'timestamp': 1504972769.564265, u'reason': u'reboot_timeout'}, u'ZX1G22WWWD': {u'timestamp': 1504972769.565158, u'reason': u'reboot_timeout'}} E 0.024s Main Unable to provision local devices. Traceback (most recent call last): File "/b/c/b/Android32_Tests__N_Nexus6_/src/third_party/catapult/devil/devil/android/tools/provision_devices.py", line 640, in main wipe=not args.skip_wipe and not args.emulators) File "/b/c/b/Android32_Tests__N_Nexus6_/src/third_party/catapult/devil/devil/android/tools/provision_devices.py", line 95, in ProvisionDevices devices = script_common.GetDevices(devices, blacklist) File "/b/c/b/Android32_Tests__N_Nexus6_/src/third_party/catapult/devil/devil/android/tools/script_common.py", line 47, in GetDevices raise device_errors.NoDevicesError() NoDevicesError: No devices attached.
,
Sep 11 2017
Right sorry.
,
Sep 11 2017
,
Sep 11 2017
You gotta love this. Looks like the devices came back on their own starting with https://build.chromium.org/p/client.webrtc.perf/builders/Android32%20Tests%20%28N%20Nexus6%29/builds/3464 |
|||
►
Sign in to add a comment |
|||
Comment 1 by d...@chromium.org
, Sep 11 2017