akeshet@akeshet:~$ stable_version cyan
Chrome OS cyan R68-10718.34.0
Firmware cyan Google_Cyan.7287.57.165
FAFT cyan cyan-firmware/R46-7287.57.180
akeshet@akeshet:~$ stable_version -t cros cyan R69-01863.0.0
Updating Chrome OS cyan -> R68-10718.34.0 to R69-01863.0.0
akeshet@akeshet:~$ stable_version cyan
Chrome OS cyan R69-01863.0.0
Firmware cyan Google_Cyan.7287.57.165
FAFT cyan cyan-firmware/R46-7287.57.180
Stable image updated.
Note that I don't see the "firmware" iamge having changed after that command. I'm not sure if this is because there is some time lag for another service to realize that the image provides a new firmware, or if that firmware mapping entry is simply ignored, or what.
> Note that I don't see the "firmware" iamge having changed after that command.
That's because there's a typo. The correct version should
be R69-10863.0.0, not R69-01863.0.0.
> this update will not be reflected until the next 4am tuesday cronjob, unless we run that manually. Is that correct?
No, manual updates take effect immediately.
Oh. I see I own the bug... Fixing the assigned repair image is
actually kind of important to do right away. It wouldn't take long
for that to start breaking DUTs.
$ stable_version -t cros cyan R69-10863.0.0
Updating Chrome OS cyan -> R69-01863.0.0 to R69-10863.0.0
Updating Firmware cyan -> Google_Cyan.7287.57.165 to Google_Cyan.7287.57.180
$ atest host list chromeos2-row10-rack7-host1 | count_labels -p
1 chameleon_hdmi_unstable
Meaning <sigh> the failure to update is caused by bug 861867 .
We should track the cyan update (or lack thereof) on that bug; this
ticket has been addressed.
Comment 1 by davidri...@chromium.org
, Jul 10