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

Issue 866131 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Android: set overheating devices as maintenance, not quarantine

Project Member Reported by mar...@chromium.org, Jul 20

Issue description

<from discussion with Simon>

For swarming, a quarantined bot is alive but in an unrecoverable brokenness.

Historically, we used to set hot devices as quarantined so that they would stay alive but not get tasks.

The challenge is that quarantine, for Swarming, means broken, so that if there's exactly one bot that can run a task and the device is overheating, the server will deny the task with NO_RESOURCE.

In practice, hot temperature can be considered "maintenance downtime", so this makes "sense" if you think hard enough. :)
 
Cc: dtu@chromium.org
Owner: bpastene@chromium.org
Status: Assigned (was: Available)
*thinks*

Nope.

*thinks harder*

Mmmm maybe...

*thinks harderer*

Ok, I guess it makes sense. I'll tweak it.


Project Member

Comment 3 by bugdroid1@chromium.org, Jul 24

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/81793d006d8154be4c27fa50b9b05a771b9784a6

commit 81793d006d8154be4c27fa50b9b05a771b9784a6
Author: Ben Pastene <bpastene@chromium.org>
Date: Tue Jul 24 00:49:12 2018

Project Member

Comment 4 by bugdroid1@chromium.org, Jul 24

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/172f6ec438c50a375e1f59f2c1ff06b4d3a81f1e

commit 172f6ec438c50a375e1f59f2c1ff06b4d3a81f1e
Author: Ben Pastene <bpastene@chromium.org>
Date: Tue Jul 24 20:40:12 2018

Sign in to add a comment