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

Issue 650249 link

Starred by 1 user
Status: Fixed
Owner:
vhang@chromium.org
Closed: Sep 2016
Cc:
█ rnep...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: ----



Sign in to add a comment

provision_devices failing on build77-b7

Project Member Reported by sullivan@chromium.org, Sep 26 2016 
Link to buildbot status page:
https://uberchromegw.corp.google.com/i/internal.tryserver.clankium/builders/clankium_perf_bisect_fyi/builds/247

I see a lot of this in the logs:

I 17274.288s TimeoutThread-1-for-ProvisionDevice(00d21e2e89f32af5)  [host]> /b/build/slave/clankium_perf_bisect_fyi/build/src/third_party/android_tools/sdk/platform-tools/adb -s 00d21e2e89f32af5 shell '( dumpsys battery );echo %$?'
I 17274.389s ProvisionDevice(00d21e2e89f32af5)  Current battery temperature: 582
I 17274.389s ProvisionDevice(00d21e2e89f32af5)  condition 'cool_device' not met

Randy, should labs team try swapping out the device?

Comment 1 by rnep...@chromium.org, Sep 26 2016 

The temperature was going up, so we know it not that the sensor isn't being updated for some reason. At the very least labs needs to look at the device, make sure the battery isn't damaged and then make sure the device is positioned in a way that the heat can escape. If it fell between other devices it'll never cool, for example.

Comment 2 by d...@chromium.org, Sep 26 2016 

There was a thermal event last night in the lab, the network is down currently and machines will need to be visited to bring them back up. (https://crbug.com/650141)

That would explain why the temperature was through the roof on the last run of the bot.

Comment 3 by vhang@chromium.org, Sep 26 2016

Owner: vhang@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by vhang@chromium.org, Sep 26 2016 

I checked on the 1 N5X that was connected to this bot.  It seems to be healthy and responsive.  adb seemed to have detected the device:

List of devices attached 
00d21e2e89f32af5       device usb:2-1.2 product:bullhead model:Nexus_5X device:bullhead

Not sure what else we can do to help.  Please let us know how to proceed.

Comment 5 by rnep...@chromium.org, Sep 26 2016 

The device wasn't unresponsive. It was determined by provision_devices to be too hot to continue running tests. There is nothing to do now except monitor and make sure the device is cool next time something is ran on it.

Running adb shell -s <device> dumpsys battery and seeing the temperature is low enough to run tests is probably a good enough indicator to close the bug.

Comment 6 by vhang@chromium.org, Sep 26 2016

Status: Fixed (was: Assigned)
The temperature should be down now.  I'll close this bug but please reopen if you still see any problems.
►

Sign in to add a comment