commit | f9d5ba2441d8d383c47b9476b91040b2ef4e97f5 | [log] [tgz] |
---|---|---|
author | Harry Pan <harry.pan@intel.com> | Sat Dec 21 01:47:26 2019 +0800 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 17 03:47:12 2020 +0000 |
tree | c195843fe60ea9ffe2e15cee39a4b5162d0c52e5 | |
parent | 786fad0cf0d5eef97021acb7b71e9db2da130771 [diff] |
power_status: platform-agnostic wraparound detection for RC6 residency Do not assume the rc6_residency_ms of sysfs is monotonically increasing, instead, scarify the precision of residency polling to avoid negative residency duration. To archive this, cache a previous RC6 residency to detect wraparound, apply delta to current residency then cache it to an accumulated RC6 residency since the object created; therefore, we make the accumulated RC6 in monotonically increasing in userspace. In theory, the worst-case affecting RC6 portion per loop is the polling period divide by loop period; assuming PLT in 20 seconds polling per one hour loop, it affects RC6 ratio about -0.005 (-0.5%) in a worst-case. BUG=chromium:1033843, b:145623577 TEST=do long PLT, at least two hours for big-core, one for small-core, examine report, focus on RC0/RC6, make sure the metric has no negative residency which would affect the diagram of power_log.html, instead by wraparound detection warning in the autotest debug logs. Change-Id: I1e3f3abc8fa7fb4661ed650cc8bd665f87da5e12 Signed-off-by: Harry Pan <harry.pan@intel.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1978046 Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org> Reviewed-by: Puthikorn Voravootivat <puthik@chromium.org> Tested-by: Puthikorn Voravootivat <puthik@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.