New issue
Advanced search Search tips

Issue 739373 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Chromedriver Android bot : No devices attached on build91-b1

Project Member Reported by gmanikpure@chromium.org, Jul 5 2017

Issue description

https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29 has been failing since yesterday.

 VPYTHON_VIRTUALENV_ROOT: /b/c/vpython
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.067s Main  No available devices to provision.
E    0.068s Main  Local device blacklist: {u'0757a2f000599749': {u'timestamp': 1499263614.963676, u'reason': u'reboot_timeout'}}
E    0.068s 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 652, 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 96, 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 27, in GetDevices
    raise device_errors.NoDevicesError()
NoDevicesError: No devices attached.


Could someone please look into it? Thanks.
 
Owner: pschmidt@chromium.org
Status: Started (was: Untriaged)
The N5 was wedged.  Power cycled it and now it's back.

chrome-bot@build91-b1:(Linux 14.04):~$ ./adb devices
List of devices attached
0757a2f000599749	device

Effective with https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/34940
Thank you!
Status: Fixed (was: Started)
Status: Untriaged (was: Fixed)
This issue is back again. Hence, reopening.

https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/35434

Could someone please look into it? Thanks.
We need this bot to be working for Chromedriver regression testing.

Can someone please look into this? Please let me know if a new bug needs to be filed.
Status: Assigned (was: Untriaged)
When reopening remove the owner so someone else can pick it up.

Looking at this now.
Status: Fixed (was: Assigned)
The N5 was wedged.  Power cycled it and now it's back.   Effective with https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/35615
re comment#6, Noted.

Thanks for fixing it :)
Owner: ----
Status: Untriaged (was: Fixed)
This issue is back again. Can someone please look into it?

https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/35640
Owner: pschmidt@chromium.org
Status: Assigned (was: Untriaged)
Device was wedged again.  This time I re-flashed it.

If it happens again I'll replace it.

Does it need to be a N5 running KTU84P ?
re comment#10, Yes, device needs to be running on Android 4.4 (KitKat).
Thanks.
Hi Peter, thanks for re-flashing the device. It is up and running again.

But unfortunately, we have another problem. Chrome versions are older and therefore the tests are failing.

John helped to successfully update the beta apk but while installing Chrome stable apk, "Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]" is displayed.

The steps he already tried:
1) To remove Chrome from the device-
adb root
adb remount
adb shell rm -rf /system/app/Chrome.apk

2) To install :
./adb install -rg ChromeStable.apk

Do you have any idea how "Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]" can be resolved?
I looked at the device and it thought it still had chromebeta installed.  Then went to Settings -> Apps and uninstalled it from there.

Is android-B0urB0N%2F60.0.3112.97%2Farm%2FChromeStable.apk what you need installed?
Yes, android-B0urB0N%2F60.0.3112.97%2Farm%2FChromeStable.apk is the right apk to install. Thanks.
Done.  Looks like it installed.
Status: Fixed (was: Assigned)
Closing as device has been up
Owner: ----
Status: Untriaged (was: Fixed)
This issue is back again. Can someone please look into it?

https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/36281

Comment 18 by jo...@google.com, Sep 18 2017

Owner: jo...@chromium.org
Status: Assigned (was: Untriaged)
N5 was wedged.  Had to power cycle it.

chrome-bot@build91-b1:(Linux 14.04):~$ ./adb devices
List of devices attached
0757a2f000599749	device
Status: Verified (was: Assigned)
Thanks, tests are running fine now.

Sign in to add a comment