| commit | 24e3b6e0012669b88dd5b140b51a56220026eb96 | [log] [tgz] |
|---|---|---|
| author | Kevin Shelton <kmshelton@chromium.org> | Tue Jun 26 17:43:32 2018 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Jun 28 21:06:15 2018 -0700 |
| tree | 5d64b5653f47e2d836cb46f9b38e2f9aa70ade33 | |
| parent | 7854a62acdb7c54a14d40c042e1b2f106dfa10f6 [diff] |
firmware_LockedME: accomodate new flashrom behavior Recent changes to the CrOS version of flashrom result in writes to flash regions protected by the PCH (when instructed by the contents of SI_DESC) to not result in a failed exit status, but still fail to write* (good) and log an access failure (observed on both an Intel big core SoC and Intel small core SoC). The CrOS flashrom maintainer should make some level of effort to couple flashrom behavior changes with faft: so, if the behavior changes back to an exit status of zero, this change should be reverted at the same time (it should be innocuous in that case, but to avoid build up of detritus in this test). *fail to write observation is based on the log of the access failure and read attempts of protected regions still being all ones. BUG=b:110839551, b:110572221 TEST=Ran against a small core DUT (epaullete) with a locked TXE (passed as would be expected). Ran against a big core DUT (pantheon) with the manufacturing mode check commented out (failed as expected with SI_DESC detected as writeable). Change-Id: I83ec216fcb6018961077a3052d54b771a2ec4182 Reviewed-on: https://chromium-review.googlesource.com/1116192 Commit-Ready: Kevin Shelton <kmshelton@chromium.org> Tested-by: Kevin Shelton <kmshelton@chromium.org> Reviewed-by: Martin Roth <martinroth@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.