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

Issue 678672 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

rethink servo host reboot repair action for servo v4 duts

Project Member Reported by kevcheng@chromium.org, Jan 5 2017

Issue description

sometimes the servo v4/uServo will fail to initialize for a variety of reasons and none of the repair actions will fix it, so it will try to reboot the servo host as a last resort.  This isn't desirable when only one servo is in this failed state but the others are ok since the DUT will inevitably get into a repair loop and if the reboot doesn't help, will continually lock the duts that aren't affected.

I think the last resort reboot should only be done if all the duts are affected vs just 1. 
 
And just to add another point, a lot of the repair actions that are effective is reconnecting the servo to the DUT (primarily between the uServo).
Status: Archived (was: Assigned)
Bulk closing Infra>Client>ChromeOS issues untouched in over a year.

Sign in to add a comment