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

Issue 787521 link

Starred by 1 user
Status: Verified
Owner:
█ pschmidt@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Cc:
johnchen@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

build91-b1: No devices attached (Chromedriver Android bot)

Project Member Reported by khachatryan@chromium.org, Nov 21 2017 
The Android waterfall is currently down, because the attached device has stopped working

Comment 1 by khachatryan@chromium.org, Nov 21 2017

Labels: -Pri-3 Pri-1

Comment 2 by khachatryan@chromium.org, Nov 21 2017

Labels: -Pri-1 Pri-2

Comment 3 by pschm...@google.com, Nov 21 2017 

Can you provide a link to the failing builder?

Comment 6 by khachatryan@chromium.org, Nov 21 2017 

The logs from Waterfall Android Build Bot:

 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

Comment 8 by tandrii@chromium.org, Nov 21 2017

Labels: -Infra-Troopers
Summary: build91-b1: No devices attached (Chromedriver Android bot) (was: Chromedriver Android bot : No devices attached)

Comment 9 by pschm...@google.com, Nov 21 2017

Owner: pschmidt@chromium.org
Status: Fixed (was: Available)
The N5 was unresponsive.  Power cycled it.

List of devices attached
0757a2f000599749	device

Comment 10 by khachatryan@chromium.org, Nov 21 2017 

OK, thank you.
I'll close ticket as soon as tests will detect the device and run.

Comment 11 by khachatryan@chromium.org, Nov 21 2017

Status: Verified (was: Fixed)
Tests are running.
Verified. Tests are running.
►

Sign in to add a comment