Chromedriver Android bot is failing at provision_devices step |
|||||||||||
Issue descriptionChromedriver Android bot is failing at provision_devices step since Saturday. https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/32403 I 0.006s 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.070s Main Unable to provision local devices. Traceback (most recent call last): File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/build/android/provision_devices.py", line 553, in main return ProvisionDevices(args) File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/build/android/provision_devices.py", line 74, in ProvisionDevices raise device_errors.DeviceUnreachableError(args.device) DeviceUnreachableError: None step returned non-zero exit code: 87 @@@STEP_EXCEPTION@@@ Could someone please look into it?
,
Feb 13 2017
The N5 died. There are no signs of life. Charging up a replacement.
,
Feb 13 2017
Replacement installed. chrome-bot@build91-b1:(Linux 14.04):~$ ./adb devices List of devices attached 0757a2f000599749 device Starting with https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/32501
,
Feb 13 2017
Thanks for fixing it! Bot is up and running. However, there are some test failures due to the chrome versions. @ Sam, Looks like we might need to update Chrome apks on the new device. Could you please take a look?
,
Feb 16 2017
The beta apk installs fine, but the stable one fails with this error:
[100%] /data/local/tmp/android-B0urB0N%2F56.0.2924.87%2Farm%2FChromeStable.apk
pkg: /data/local/tmp/android-B0urB0N%2F56.0.2924.87%2Farm%2FChromeStable.apk
Failure [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES]
jbudorick@ I remember we had this issue last time we replaced the device, and you fixed it by installing with a certain adb switch. Can you remind me how you did this?
,
Feb 16 2017
Also, I tried doing what was suggested in crbug.com/650301#c8 (including using the symlinked adb) but I still get Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
,
Feb 24 2017
I've just updated both the stable and beta apks. The magic switch was "-g": ./adb install -rg ChromeStable.apk
,
Mar 3 2017
Chromedriver android bot again started failing this morning. https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/32727 I 0.005s 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.069s Main Unable to provision local devices. Traceback (most recent call last): File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/build/android/provision_devices.py", line 553, in main return ProvisionDevices(args) File "/b/build/slave/Android_ChromeDriver_Tests__dbg_/build/src/build/android/provision_devices.py", line 74, in ProvisionDevices raise device_errors.DeviceUnreachableError(args.device) DeviceUnreachableError: None step returned non-zero exit code: 87 Can someone please take a look?
,
Mar 3 2017
Looking into this. I personally know very little about android device provisioning, so I'm talking to bpastene and jbudorick.
,
Mar 3 2017
+ labs Looks like the N5 on build91-b1 is down/could use some TLC
,
Mar 3 2017
Device was frozen. Power cycled and now it's back. chrome-bot@build91-b1:(Linux 14.04):~$ ./adb devices List of devices attached 0757a2f000599749 device
,
Mar 3 2017
I just updated the beta apk again, to 57.0.2987.88. Hopefully it cycles green with build #32731.
,
Mar 3 2017
,
Mar 3 2017
Green!
,
Mar 3 2017
Thanks for fixing it! |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by pschmidt@chromium.org
, Feb 13 2017Status: Assigned (was: Untriaged)