chromeos-firmwareupdate should preserve RW_ELOG |
|||||
Issue descriptionI think we talked about this before but didn't really open a bug, and I just noticed it again in a feedback report. Filing this so we don't forget about it. Approach is to do essentially the same thing as https://chromium-review.googlesource.com/319600 for RW_ELOG. Goal is that the eventlog won't get cleared by the update.
,
Oct 25 2016
,
Aug 18 2017
,
Aug 20
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 26
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/vboot_reference/+/dd4f275b3f81a58c28c9a388590a67ddeb493afc commit dd4f275b3f81a58c28c9a388590a67ddeb493afc Author: Hung-Te Lin <hungte@chromium.org> Date: Wed Sep 26 17:32:05 2018 futility: update: Preserve RW_ELOG The eventlog is stored in RW_ELOG and should not be destroyed during firmware update. BUG= chromium:655423 TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility BRANCH=None Change-Id: I0b4fe1e78ae2d499e985471f51cfa9eb983c8adc Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1242663 Reviewed-by: Julius Werner <jwerner@chromium.org> [modify] https://crrev.com/dd4f275b3f81a58c28c9a388590a67ddeb493afc/futility/cmd_update.c
,
Sep 26
Woohoo, it took less than 2 years! ;) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jwer...@chromium.org
, Oct 20 2016