| commit | 951f357958e218221c1555dede04e896275bbc71 | [log] [tgz] |
|---|---|---|
| author | Brian Norris <briannorris@chromium.org> | Wed Jan 16 10:13:03 2019 -0800 |
| committer | Brian Norris <briannorris@chromium.org> | Fri Jan 18 01:26:08 2019 +0000 |
| tree | 2d43b9a4d6505c9a70184ab4068c88f1460e3457 | |
| parent | 757626d8db2d879247a50591894af639cb7259bb [diff] |
[autotest] utils: improve CPU max freq robustness CPUs can come online/offline at arbitrary times, especially on some Tegra CPUs. This causes problems in utils.get_cpu_max_frequency() as follows: * the 'ls /sys/.../cpu*/' glob might match some set of CPU paths in the shell glob, but those paths might not all be there by the time 'ls' runs, and so 'ls' will totally fail (rather than, say, printing the subset of CPUs that are still there). To fix this, we can just 'echo' the glob result back, and ensure that it matched at least 1 valid path. * when iterating on paths returned from utils._get_cpufreq_paths(), the path may no longer exist, causing IOErrors in _get_float_from_file(). We should just ignore these errors, as long as we get some valid max frequency from some other CPU. With those fixes, we shouldn't see any further failures, unless completely disjoint sets of CPUs show up at different times, causing us to fail to read any single CPU properly. This shouldn't happen, since CPU0 should always exist. CL:1128445 already sorta noticed this problem, but it didn't extend its pattern to existing cpufreq use cases. Additionally, let's add a much clearer exception if a test is trying to retrieve the max CPU frequency on a system where cpufreq isn't supported (i.e., there are no cpufreq paths available). This may have come up on deprecated boards (see chromium:867320)? BUG=chromium:920263 TEST=graphics_Gbm, on nyan-big and others Change-Id: I9014cd48cb2c268001e8bbbb098aed8b4104bd2e Reviewed-on: https://chromium-review.googlesource.com/c/1415676 Reviewed-by: Ilja H. Friedel <ihf@chromium.org> Tested-by: Brian Norris <briannorris@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.