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

Issue 652742 link

Starred by 1 user
Status: Archived
Owner:
█ kevcheng@chromium.org
Last visit > 30 days ago
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Repair can't restart servod

Reported by jrbarnette@chromium.org, Oct 4 2016 
When a servo host is failing verify(), one of the repair
actions includes this command:
    start servod BOARD=... PORT=...

That command seems not reliable in all cases.  I just saw this
on a servo V3:
    localhost ~ # start servod BOARD=whirlwind PORT=9999
    start: Job failed to start
    localhost ~ # start servod PORT=9999
    servod (9999) start/running, process 4147
    localhost ~ # 

I can't explain it, but it causes servo not to repair in
certain cases.

Comment 1 by akes...@chromium.org, Jul 17 2017

Labels: akeshet-pending-downgrade
ChromeOS Infra P1 Bugscrub.

P1 Bugs in this component should be important enough to get weekly status updates.

Is this already fixed?  -> Fixed
Is this no longer relevant? -> Archived or WontFix
Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority.
Is this a Feature Request rather than a bug? Type -> Feature
Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign.
Does this bug have the wrong owner? -> reassign.

Bugs that remain in this state next week will be downgraded to P2.

Comment 2 by sosa@chromium.org, Jul 18 2017

Status: Archived (was: Assigned)
►

Sign in to add a comment