| f040ac27bb7d6086fa6f7cc4b9d4d8e789adfd60 |
|
05-Aug-2015 |
Derek Basehore <dbasehore@chromium.org> |
power_LoadTest: remove old unsupported tasks variables
This removes the old task variables for control and control.1hour. The
format for those variables has changed, so these are no longer useful.
BUG=chromium:515240
TEST=run power_LoadTest control.1hour
Change-Id: I807042ffcd11a5e4cae971cebe0a59b8113b0d99
Reviewed-on: https://chromium-review.googlesource.com/290622
Reviewed-by: Eric Caruso <ejcaruso@chromium.org>
Tested-by: Derek Basehore <dbasehore@chromium.org>
Commit-Queue: Derek Basehore <dbasehore@chromium.org>
/external/autotest/client/site_tests/power_LoadTest/control.1hour
|
| c28bce12fc7ddc12effcac21afce4ef5c174d4f3 |
|
07-Mar-2014 |
Todd Broch <tbroch@chromium.org> |
power: Convert control name fields for test_that usage.
CL to convert the remaining power_*/control.<suffix> files NAME fields
to <test>.<suffix> so they can be properly dispatched by test_that.
BUG=none
TEST=run via test_that and see tests dispatch properly.
test_that <host> power_AudioDetector.10s
test_that <host> power_CheckAfterSuspend.TPMCheckStress
test_that <host> power_LoadTest.1hour
test_that <host> power_ProbeDriver.probe_ac
test_that <host> power_ProbeDriver.probe_bat
test_that <host> power_Resume.resume_constraint
Change-Id: I45c33f1c0d5170dc31883b0e87cd9251f1852985
Reviewed-on: https://chromium-review.googlesource.com/189230
Reviewed-by: Sameer Nanda <snanda@chromium.org>
Tested-by: Todd Broch <tbroch@chromium.org>
Commit-Queue: Todd Broch <tbroch@chromium.org>
/external/autotest/client/site_tests/power_LoadTest/control.1hour
|
| 59405505bdf7284425645edc162436fd89fb6d51 |
|
03-Dec-2013 |
Derek Basehore <dbasehore@chromium.org> |
Revert "autotest: Migrate power_LoadTest to WifiProxy" and import new path
There is an issue with the wifi_config object getting serialized, so I'm
reverting this while I rewrite the change. The old import statement for
flimflam is now broken. This imports the test path for flimflam to fix that.
BUG=chromium:322383
TEST=run power_daily suite in the lab
This reverts commit 08d2ef629684a3269bb4d7ea16d05e175c47cbe4.
Change-Id: I92cc969066574ad0018e5f46b355a1191fa6ae56
Reviewed-on: https://chromium-review.googlesource.com/178549
Reviewed-by: Derek Basehore <dbasehore@chromium.org>
Commit-Queue: Derek Basehore <dbasehore@chromium.org>
Tested-by: Derek Basehore <dbasehore@chromium.org>
/external/autotest/client/site_tests/power_LoadTest/control.1hour
|
| 08d2ef629684a3269bb4d7ea16d05e175c47cbe4 |
|
26-Nov-2013 |
Christopher Wiley <wiley@chromium.org> |
autotest: Migrate power_LoadTest to WifiProxy
Something changed with the flimflam test module, so just migrate over to
shill_proxy to fix the problem since the flimflam test module is depreciated.
BUG=chromium:322383
TEST=manual and check if power_LoadTest still fails when run in the lab
Change-Id: I7d72eb50fc7aa1e954d1a464fe9d59772ede6f58
Reviewed-on: https://chromium-review.googlesource.com/178092
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Derek Basehore <dbasehore@chromium.org>
Tested-by: Derek Basehore <dbasehore@chromium.org>
/external/autotest/client/site_tests/power_LoadTest/control.1hour
|
| 21978453eaa14e284560915268cf9cb1b4604a48 |
|
03-Nov-2012 |
Todd Broch <tbroch@chromium.org> |
autotest: Extrapolate minutes_battery_life for power_LoadTest.
In its current form power_LoadTest reports minutes_battery_life as the
number of minutes the battery lasted running the multiple iterations
of the 1 hour 60/20/10/10 payload.
While performing the test over the fully charged to fully discharged
battery is vital as what real world use will be it makes it hard to
get the results due to long runtime. Additonally even over the full
discharge there are small inaccuracies depending upon how charged the
battery was or what level we allowed it to discharge to that are
currently not accounted for.
This change extrapolates the minutes_battery_life_tested by applying
the following equation:
minutes_battery_life = minutes_battery_life_tested * scale -
low_battery_seconds
scale = (wh_energy_full_design / wh_energy_used) * usable_battery
usable_battery = (1 - low_battery_percent)
Where:
wh_energy_used = ah_charge_used * MEAN(v_voltage)
low_battery_percent & low_battery_seconds are values determined by
power manager. Note, only one will be non-zero.
This change should fix / allow the following:
1. More accurate battery_life estimates over the life of a battery.
A fresh battery that can be overcharged will not benefit nor will a
tired battery penalize the results.
2. Runs < full drain. As such I'm adding a control file for 1 hour
run with plan to add it to nightly
BUG=chromium-os:35824
TEST=run test for 1hr using control.1hour
Change-Id: I24eb65a93d9b1a8ed79103e9ab623f0ce22269c9
Reviewed-on: https://gerrit.chromium.org/gerrit/37318
Commit-Ready: Todd Broch <tbroch@chromium.org>
Reviewed-by: Todd Broch <tbroch@chromium.org>
Tested-by: Todd Broch <tbroch@chromium.org>
/external/autotest/client/site_tests/power_LoadTest/control.1hour
|