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

Issue 592616 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Device Offline on chromium.perf: Android Nexus 9 Perf (2)

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

Issue description

Link to buildbot status page:
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus9%20Perf%20%282%29/builds/1205


Device:
HT4B7JT01059 blacklisted



Traceback (most recent call last):
  File "/b/build/slave/Android_Nexus9_Perf__2_/build/src/build/android/buildbot/bb_device_status_check.py", line 240, in RecoverDevices
    reset_usb.reset_android_usb(serial)
  File "/b/build/slave/Android_Nexus9_Perf__2_/build/src/build/android/devil/utils/reset_usb.py", line 48, in reset_android_usb
    'Unable to determine bus or device for device %s' % serial)
DeviceUnreachableError: Unable to determine bus or device for device HT4B7JT01059
 

Comment 1 by vhang@google.com, Mar 7 2016

Labels: Infra-Labs-Hwops Pri-2
Status: Available (was: Untriaged)
Adding to Hwops queue

Comment 2 by shazrat@google.com, Mar 7 2016

Owner: shazrat@google.com
Status: Fixed (was: Available)
Device was offline upon inspection. However, it booted up fine.

chrome-bot@build12-b1:~$ /b/build_internal/scripts/slave/android/adb devices
List of devices attached 
HT4B6JT02657	device
HT4B7JT01232	device
HT4B7JT01277	device
HT4B7JT01981	device
HT4B7JT01243	device
HT4B6JT02450	device
HT4B7JT01059	device
Status: Assigned (was: Fixed)
Can we keep this open until it's confirmed the devices are back online and working?

Comment 4 by shazrat@google.com, Mar 8 2016

Yes absolutely. I'll do this for future bugs if its preferred.
Awesome, thanks! It looks like HT4B7JT01059 is still blacklisted :(

Comment 6 by shazrat@google.com, Mar 9 2016

I checked on it again earlier today and it was stuck on the initial setup steps (choose language, wifi network, etc), and simultaneously trying to load a webpage. This didn't match how the other devices were so I gave it another reboot. I'll check the next build output and replace the usb cable and or hub if this continues.

Comment 7 by shazrat@google.com, Mar 10 2016

I just noticed the tablet was at 51% battery so it wasn't getting enough current. I swapped out the USB cable for now and will check again, adding in a second hub if necessary.

Comment 8 by pschm...@google.com, Mar 10 2016

Cc: rnep...@chromium.org
We have seen this before.  Battery level not being updated.   There was a speculative fix in https://bugs.chromium.org/p/chromium/issues/detail?id=567786  

I'll stop by tomorrow and will take a look. 

Checking HT4B6JT02657...
Current Battery Service state:
  (UPDATES STOPPED -- use 'reset' to restart)
  AC powered: false
  USB powered: false
  Wireless powered: false
  status: 5
  health: 2
  present: true
  level: 100
  scale: 100
  voltage: 4302
  temperature: 348
  technology: Li-ion
Checking HT4B7JT01243...
Current Battery Service state:
  (UPDATES STOPPED -- use 'reset' to restart)
  AC powered: false
  USB powered: false
  Wireless powered: false
  status: 5
  health: 2
  present: true
  level: 100
  scale: 100
  voltage: 4348
  temperature: 326
  technology: Li-ion
I would try running adb -s DEVICE shell dumpsys battery reset on all suspect devices. For some reason it is getting in a state where this isn't getting called when it should be (based off the output above).

I'd do it myself but I'm OOO and have really shoddy internet connection.
I just checked and these seems to have fixed themselves I guessing from the following reboot/wipe in the next build.

Comment 11 by shazrat@google.com, Mar 10 2016

Great, thanks for the tips. I'll see if the next few builds are successful before resolving this bug.

Comment 12 by shazrat@google.com, Mar 15 2016

Status: Fixed (was: Assigned)
Last few builds have been successful. Resolving this bug.
Components: Infra>Labs>HWOps
Labels: -Infra-Labs-Hwops
Components: Infra>Labs
Labels: -Infra-Labs
Components: -Infra>Labs

Sign in to add a comment