New issue
Advanced search Search tips

Issue 836249 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

Chromedriver Android bot : No devices attached on build91-b1

Project Member Reported by khachatryan@chromium.org, Apr 24 2018

Issue description

INFRA_BUILDBOT_SLAVE_NAME: build91-b1
 LANG: en_US.UTF-8
 LOGDOG_COORDINATOR_HOST: logs.chromium.org
 LOGDOG_STREAM_PREFIX: bb/chromium.fyi/Android_ChromeDriver_Tests__dbg_/40140
 LOGDOG_STREAM_PROJECT: chromium
 LOGDOG_STREAM_SERVER_PATH: unix:/b/build/.recipe_runtime/tmp5tnPkK/butler.sock
 LOGNAME: chrome-bot
 PAGER: cat
 PATH: /b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/third_party/android_tools/sdk/platform-tools:/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/build/android:/b/cipd_path_tools:/b/cipd_path_tools/bin:/b/cipd_client:/home/chrome-bot/slavebin:/b/depot_tools:/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
 PWD: /b/build/slave/Android_ChromeDriver_Tests__dbg_/build
 PYTHONIOENCODING: UTF-8
 PYTHONPATH: /b/build/site_config:/b/build/scripts:/b/build/scripts/release:/b/build/third_party:/b/build/third_party/google_api_python_client:/b/build/third_party/httplib2/python2:/b/build/third_party/infra_libs:/b/build/third_party/oauth2client:/b/build/third_party/pyasn1:/b/build/third_party/pyasn1-modules:/b/build/third_party/python-rsa:/b/build/third_party/requests_2_10_0:/b/build/third_party/setuptools-0.6c11:/b/build/third_party/site-packages:/b/build/third_party/uritemplate:/b/build_internal/site_config:/b/build_internal/symsrc:/b/build/slave:/b/build/third_party/buildbot_slave_8_4:/b/build/third_party/twisted_10_2:
 PYTHONUNBUFFERED: 1
 SHELL: /bin/bash
 USER: chrome-bot
 VPYTHON_CLEAR_PYTHONPATH: 1
 VPYTHON_VIRTUALENV_ROOT: /b/c/vpython
I    0.003s TimeoutThread-1-for-MainThread  condition '<lambda>' met (0.0s)
I    0.003s TimeoutThread-1-for-MainThread  [host]> /b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/third_party/android_tools/sdk/platform-tools/adb devices
E    0.066s Main  No available devices to provision.
E    0.066s Main  Local device blacklist: {u'0d89323643e4b6e5': {u'timestamp': 1524581450.610261, u'reason': u'reboot_failure'}}
E    0.066s Main  Unable to provision local devices.
Traceback (most recent call last):
  File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/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/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/third_party/catapult/devil/devil/android/tools/provision_devices.py", line 95, in ProvisionDevices
    devices = script_common.GetDevices(devices, blacklist)
  File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/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
 
Components: Infra>Labs
Labels: -Infra-Troopers
Hi lab team,

Can you help to check if the device is properly attached to build91-b1?

Comment 2 by jo...@google.com, Apr 24 2018

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

Comment 3 by jo...@chromium.org, Apr 24 2018

Device's battery was completely discharged. Going to offline it and see how it takes to AC charging. Also noticed there's no HUB supporting the device, which contribute to sluggish charging. Going to hook one up now and see if it helps.

Comment 4 by jo...@chromium.org, Apr 24 2018

Status: Fixed (was: Assigned)
This is back and charging of a USB hub now.

  level: 100
  scale: 100

List of devices attached
0d89323643e4b6e5	device
Thank you.

Status: Verified (was: Fixed)

Sign in to add a comment