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

Issue 868047 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jul 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Update servo in the lab to R70-10913.0.0 or later

Reported by jrbarnette@chromium.org, Jul 26

Issue description

Because of bug 865482 and b/111658037, we have a number of
servos in the lab that are stuck.  The fix is now in the
tree:
    https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1150963

We need to update servo in the lab to pick up the fix.

The first canary with the fix won't be available until after COB
today, and tomorrow is Friday (not a good day to die), so we should
update bright and early Monday morning.

Assigning to next week's deputy for action.

 
Cc: nsanders@chromium.org englab-sys-cros@google.com
Is this affecting both beaglebone and labstation?
> Is this affecting both beaglebone and labstation?

TTBOMK, The known bugs affect only servo V4.

The standard process updates beaglebone and labstation together to
keep the same version at all times, so both will be updated.

Issue 867930 has been merged into this issue.
Cc: mruthven@chromium.org
Updated
    $ stable_version -t cros beaglebone_servo $BUILD
    Updating  Chrome OS  beaglebone_servo -> R69-10863.0.0 to R70-10923.0.0
    $ stable_version -t cros guado_labstation $BUILD
    Updating  Chrome OS  guado_labstation -> R69-10863.0.0 to R70-10923.0.0
    Unchanged Firmware   guado_labstation -> Google_Guado.6301.108.2016_10_06_1219

This will roll out to the lab over the next few hours.  Servo V4 units
can sometimes lag in updates because of bug 735619.

Status: Fixed (was: Assigned)

Sign in to add a comment