|author||Ruben Rodriguez Buchillon <email@example.com>||Tue Dec 25 11:31:31 2018 +0800|
|committer||chrome-bot <firstname.lastname@example.org>||Thu Dec 27 21:01:16 2018 -0800|
power_status: fix cpu sibling, and CPUFreq/CPUIdle clustering logic This change addresses an issue where the clustering logic for cpu sibling groups was too strict, and relied on some assumptions that don't always hold. More specifically - core_siblings_list does not have to be 'd-d' but rather can be a list of 'x,x...' where x can be 'd-d' or just d - glob.glob does not necessarily sort the output - even on a sorted output, on a system where some cores are turned off, the 2nd file does not have to correspond to cpu1 but could be cpu4 (e.g. current kukui) - cpuidle is not guaranteed to exist just because the cpu exists. So this change should make PLT/power tests a little more robust especially for early bring up. BUG=b:121465064 TEST=manual testing test_that --autoest_dir=$LOCAL_AT $IP power_LoadTest.fast Change-Id: Ief757c5815e168ed85a0f326675d7242212092e0 Signed-off-by: Ruben Rodriguez Buchillon <email@example.com> Reviewed-on: https://chromium-review.googlesource.com/1390734 Reviewed-by: Nicolas Boichat <firstname.lastname@example.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
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.