| commit | 0f0cbd4a278d3e7f5fc9519b0080a53a796e2c54 | [log] [tgz] |
|---|---|---|
| author | Chinglin Yu <chinglinyu@chromium.org> | Sat Jun 20 15:41:18 2020 +0800 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Jul 01 08:08:17 2020 +0000 |
| tree | bec6b29e46d4bc77bba8f15bb61b227409bff912 | |
| parent | 59ef5982ef81e9d246608dde515171add497e6a4 [diff] |
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>
Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.
Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:
A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.
A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.
Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.
Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.
Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.
See the guides to test_that and test_droid:
See the best practices guide, existing tests, and comments in the code.
git clone https://chromium.googlesource.com/chromiumos/third_party/autotest
See the coding style guide for guidance on submitting patches.
You need to run utils/build_externals.py to set up the dependencies for pre-upload hook tests.