| commit | e6fd41df9127af636376b34c0d88c90b925d95ed | [log] [tgz] |
|---|---|---|
| author | Kyle Shimabukuro <kyleshima@chromium.org> | Fri Dec 09 13:02:24 2022 -0800 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 14 01:10:09 2022 +0000 |
| tree | 2de8530b16f3509ddb5e3f09db58ea983371c7c4 | |
| parent | 8af3e9a8d87067aa24a2d65aabc14515d0e04cbf [diff] |
Add provisioning workaround to autoupdate_EndToEndTest Add a workaround for the provisioning issues on atlas, fizz, kalista, nami, and nocturne (where stateful is wiped due to repairing of the stateful partition when provisioning from M108 or greater to certain older milestones). The provisioning issue causes the DUTs to take a long time to come back up from reboot, and stateful to be wiped when they do due to the device detecting a corrupt stateful partition and triggering a repair sequence on startup. The tests can work around this by waiting longer for the DUT to reboot, and then re-provisioning the source version if python is missing. The provisioning issue should be fixed at some point, but this gives us some breathing room by unblocking releases until we can figure it out. BUG=b:261782079 TEST=test_that chromeos6-row7-rack22-host15 autoupdate_EndToEndTest --autotest_dir ~/chromiumos/src/third_party/autotest/files --args="update_type=delta source_release=14268.104.0 source_payload_uri=gs://chromeos-releases/stable-channel/nami/14268.104.0/payloads/chromeos_14268.104.0_nami_stable-channel_full_test.bin-gyztanlbga2tefhu5t4blimjwby6oah7 target_release=15183.66.0 target_payload_uri=gs://chromeos-releases/stable-channel/nami/15183.66.0/payloads/chromeos_14268.104.0-15183.66.0_nami_stable-channel_delta_test.bin-gyztqzdegrsgkur7h4o2rvswskitf5p2" Change-Id: I177448dae4a39992ba4a7c14e2a93bd7f82b40eb Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/4093294 Tested-by: Kyle Shimabukuro <kyleshima@chromium.org> Reviewed-by: Jae Hoon Kim <kimjae@chromium.org> Commit-Queue: Kyle Shimabukuro <kyleshima@chromium.org> (cherry picked from commit c7d0249e4703f1ce1e90794bf642f21ca85abdc7) Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/4102323
Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the ChromeOS team to validate complete system images of ChromeOS 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 ChromeOS 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 ChromeOS.
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.