diff options
| author | Hung-Te Lin <hungte@chromium.org> | 2018-08-21 23:09:57 +0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-09-05 09:15:17 -0700 |
| commit | 7fbbf2df700d0ab8f984114d535445c16a3d9699 (patch) | |
| tree | 2ea75b9ac1fd2af10a8712ff1ade23067b6446f5 /tests | |
| parent | 483fcf08acb9ad9bbedbb5f980314144260d5da4 (diff) | |
| download | vboot-7fbbf2df700d0ab8f984114d535445c16a3d9699.tar.gz | |
futility: cmd_update: Check contents before starting to update
In try-boot updating flow, we have to first check if RO content needs to be
changed or not, and do full (ro+ro) update if WP is disabled. Also, before
starting to update RW-A or RW-B, we should also check if the active system
already has same firmware contents.
An --force is also added to allow skipping the check.
BUG=chromium:875551
TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility
BRANCH=None
Change-Id: Ie2f75f9aab4696c75aedafbf45e418ee98a2a4b4
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1183654
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'tests')
| -rwxr-xr-x | tests/futility/test_update.sh | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/tests/futility/test_update.sh b/tests/futility/test_update.sh index 43de6a0e..bc2a2ec9 100755 --- a/tests/futility/test_update.sh +++ b/tests/futility/test_update.sh @@ -99,3 +99,7 @@ test_update "RW update (A->B)" \ test_update "RW update (B->A)" \ "${FROM_IMAGE}" "${TMP}.expected.a" \ -i "${TO_IMAGE}" -t --wp=1 --sys_props 1 + +test_update "RW update -> fallback to RO+RW Full update" \ + "${FROM_IMAGE}" "${TMP}.expected.full" \ + -i "${TO_IMAGE}" -t --wp=0 --sys_props 1 |