New issue
Advanced search Search tips

Issue 592666 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Android devices listed as 'unknown' on health page

Project Member Reported by bpastene@chromium.org, Mar 7 2016

Issue description

https://viceroy.corp.google.com/chrome_infra/Machines/android_devices

I believe a lot of those are small bugs in provision_devices.py or device_status_check.py that blacklist the same device multiple times, with different reasons. This seems to happen mainly with usb-related failures. I should consolidate that logic so that a device is blacklisted only once. Or, at the very least, not overwrite the correct reasons.
 
Labels: -OS-Mac OS-Android
hm, I'm not entirely sure how that would happen given the mechanism for blacklisting in both scripts, but I guess it's possible.
See the log for example, and search for device 0cbbe16d032f943e

https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/34262/steps/device_status_check/logs/stdio

Just listing that as usb_failure would be much more helpful imo
hm, good catch. You can see these after the usb_failures:

I   11.157s blacklisting_device_status(06c0dddc006affc1)  Adding 06c0dddc006affc1 to blacklist /b/build/slave/android/build/src/out/bad_devices.json for reason: unknown
I   11.157s blacklisting_device_status(060f020213c86670)  Adding 060f020213c86670 to blacklist /b/build/slave/android/build/src/out/bad_devices.json for reason: unknown
I   11.157s blacklisting_device_status(05fcaaa00ae58b8f)  Adding 05fcaaa00ae58b8f to blacklist /b/build/slave/android/build/src/out/bad_devices.json for reason: unknown
I   11.158s blacklisting_device_status(0cbbe16d032f943e)  Adding 0cbbe16d032f943e to blacklist /b/build/slave/android/build/src/out/bad_devices.json for reason: unknown
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 9 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b77e46bcf692f5106bb51d0b12bb3027b2ae6fef

commit b77e46bcf692f5106bb51d0b12bb3027b2ae6fef
Author: bpastene <bpastene@chromium.org>
Date: Wed Mar 09 01:50:55 2016

Make the status reporting of devices in status_check more verbose.

Replaces the unknowns we keep seeing with either usb_failure, missing,
or offline.

missing: Shows up in lsusb but not adb.
usb_failure: Shows up in lsusb but can't reset the device via /dev/bus.
offline: Doesn't show up in lsusb or adb.

BUG= 592666 

Review URL: https://codereview.chromium.org/1768423002

Cr-Commit-Position: refs/heads/master@{#380028}

[modify] https://crrev.com/b77e46bcf692f5106bb51d0b12bb3027b2ae6fef/build/android/buildbot/bb_device_status_check.py

Comment 6 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>Android
Labels: -Infra-Android
Status: Fixed (was: Assigned)
Most of the statuses are now provision_timeout, setup_failure, offline, etc.

Sign in to add a comment