New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 616617 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Android Chromedriver bot is failing at device_status_check step

Project Member Reported by gmanikpure@chromium.org, Jun 1 2016

Issue description

Device has been dead for over 17 hours now. Could someone please take a look?
Labels: -Pri-3 Pri-1
Since it is blocking Chromedriver release, increasing the priority to P1.
Owner: pschmidt@chromium.org
Status: Started (was: Untriaged)
chromeperf80 has been migrated to a new slave on the b-lab per https://buganizer.corp.google.com/issues/28868710

Just submitted https://codereview.chromium.org/2033813003 to complete this.
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 2 2016

Thank you for looking into this.
But unfortunately again the bot run has failed and this time at a different step 'provision_devices '

https://build.chromium.org/p/chromium.fyi/builders/Android%20ChromeDriver%20Tests%20%28dbg%29/builds/28227
There was a device auth. issue.  I just fixed up the keys.

The next build should be better.
Status: Verified (was: Started)
Thank you! Bot looks good now.

Sign in to add a comment