New issue
Advanced search Search tips

Issue 762879 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

No devices attached for build36-b3

Project Member Reported by ehmaldonado@chromium.org, Sep 7 2017

Issue description

Android32 Tests (L Nexus6) has been failing on the provision_devices step:

E    0.013s Main  No available devices to provision.
E    0.013s Main  Local device blacklist: {u'ZX1G22LLPD': {u'timestamp': 1504770717.107885, u'reason': u'reboot_timeout'}, u'ZX1G22KFQZ': {u'timestamp': 1504770687.614619, u'reason': u'reboot_timeout'}}
E    0.017s Main  Unable to provision local devices.
Traceback (most recent call last):
  File "/b/c/b/Android32_Tests__L_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__L_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__L_Nexus6_/src/third_party/catapult/devil/devil/android/tools/script_common.py", line 47, in GetDevices
    raise device_errors.NoDevicesError()
NoDevicesError: No devices attached.
step returned non-zero exit code: 87

Logs at https://build.chromium.org/p/client.webrtc.perf/builders/Android32%20Tests%20%28L%20Nexus6%29/builds/4111/steps/provision_devices/logs/stdio
 
Owner: pschmidt@chromium.org
Status: Assigned (was: Untriaged)
The devices were removed per t/28458720.

I'll charge up and flash replacements.
Status: Fixed (was: Assigned)
New devices are:

List of devices attached
ZX1G426FNN	device
ZX1G428PNN	device

Will be effective starting with https://build.chromium.org/p/client.webrtc.perf/builders/Android32%20Tests%20%28L%20Nexus6%29/builds/4123
Thanks!
Status: Untriaged (was: Fixed)
This is happening again.

It also looks like the devices are flaky:
https://build.chromium.org/p/client.webrtc.perf/builders/Android32%20Tests%20%28L%20Nexus6%29?numbuilds=200

Comment 6 by vhang@chromium.org, Oct 3 2017

Owner: jo...@chromium.org
Status: ass (was: Untriaged)

Comment 7 by vhang@chromium.org, Oct 3 2017

Status: Assigned (was: ass)

Comment 8 by vhang@chromium.org, Oct 3 2017

Owner: vhang@chromium.org

Comment 9 by vhang@chromium.org, Oct 9 2017

Checked both phones.  They both looked healthy.  Both phones seemed responsive.

chrome-bot@build36-b3:(Linux 14.04):~$ ./adb devices -l
List of devices attached
ZX1G426FNN             device usb:1-2.2 product:shamu model:Nexus_6 device:shamu
ZX1G428PNN             device usb:1-2.1 product:shamu model:Nexus_6 device:shamu

Tests looks like they've been green since the 29th of September.  How should we proceed?



Status: WontFix (was: Assigned)
Yeah, it looks good now.
There's no action needed, then.
Thanks!

Sign in to add a comment