tree bec6b29e46d4bc77bba8f15bb61b227409bff912
parent 59ef5982ef81e9d246608dde515171add497e6a4
author Chinglin Yu <chinglinyu@chromium.org> 1592638878 +0800
committer Commit Bot <commit-bot@chromium.org> 1593590897 +0000

autotest: make rootfs verification check optional in boot perf test.

In bug 1048050, we check and restore rootfs verification for
BootPerfServerCrosPerf to stabilize the test on crosbolt. This is done
by reimaging the DUT to the current version. Unfortunately, the attempt
to reimage hangs when developers run the test locally. Developers also
don't want a reboot test to automatically re-image their DUT since it
may have local changes they are attempting to test.

This CL provides an option "skip_rootfs_check" (default false) that
allows local runs with dev-built images to bypass the check and reimage.
platform_BootPerfServer.bootperf (control.bootperf) sets this option
to True since it's run by the bootperf script and is targeted at local
development, where rootfs is often read-write.

Example:
test_that --board=${BOARD} --args='skip_rootfs_check=True' $DUT \
BootPerfServerCrosPerf

BUG=chromium:1097086
TEST=Run BootPerfServerCrosPerf w/wo the option.
TEST=Run platform_BootPerfServer.bootperf to verify it doesn't check
rootfs verification.
TEST=bootperf -o /tmp/bootperf.results <DUT>

Change-Id: I2470d93b4cc8c4de29958f55f0ff32bc02c08ce9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2256108
Reviewed-by: Grant Grundler <grundler@chromium.org>
Commit-Queue: Chinglin Yu <chinglinyu@chromium.org>
Tested-by: Chinglin Yu <chinglinyu@chromium.org>