Cross Reference: /external/autotest/client/site_tests/power_LoadTest/power

History log of /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
Revision	Date	Author	Comments (<<< Hide modified files) (Show modified files >>>)
06ed53a4b7da6f629cb6a4076ed27ff5f07ddccb	30-Nov-2016	Danny Chan <dchan@google.com>	Make power load test backward compatible to older OS (<57). - use old method of log parsing if low_battery_shutdown* option is not available. - The log parsing option can be removed once 57 gone stable BUG=chrome-os-partner:60374 TEST=on Orco device with 56 and 57 Change-Id: Ibfbebb74e4b93a98483f32e0314e190caad7558d Reviewed-on: https://chromium-review.googlesource.com/414259 Commit-Ready: danny chan <dchan@chromium.org> Tested-by: danny chan <dchan@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
8b4fdc2687016da15a37da7767bc97d97186f647	22-Nov-2016	Daniel Erat <derat@chromium.org>	autotest: Make power_LoadTest not read powerd's logs. Update powerd_LoadTest to get powerd's low-battery shutdown thresholds from the check_powerd_config tool instead of by grepping through /var/log/power_manager/powerd.LATEST. BUG=chromium:658769 TEST=ran powerd_LoadTest.fast and verified that results display correct shutdown thresholds when powerd is configured for either time- or percent-based shutdown Change-Id: I9f420294d9e1f63c90de8b64c3cd12d95383692c Reviewed-on: https://chromium-review.googlesource.com/413704 Commit-Ready: Dan Erat <derat@chromium.org> Tested-by: Dan Erat <derat@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
f364c1d04857e2f5bd20eb5fed2500cf81fbbdbe	11-Oct-2016	Ruben Rodriguez Buchillon <coconutruben@chromium.org>	power_LoadTest: page-load-time now works on multiple-loops-plt First iteration of page-load-time had a type-error when appending multiple runs into the keyvals. We also never cleared the page-load data inside the script. Both are fixed now, and multi-loop behaves as intended. BUG=None TEST=power_LoadTest multiple-loop entry example: INVALID_ext_ms_page_load_time_max{perf}=7044.00_7341.00 INVALID_ext_ms_page_load_time_mean{perf}=2479.55_3139.45 INVALID_ext_ms_page_load_time_min{perf}=165.00_1364.00 INVALID_ext_ms_page_load_time_std{perf}=2053.79_1816.41 Change-Id: Ia6c97e3dd6cc68894cb68646318fbaffc0f25749 Reviewed-on: https://chromium-review.googlesource.com/396615 Commit-Ready: Ruben Rodriguez Buchillon <coconutruben@chromium.org> Tested-by: Ruben Rodriguez Buchillon <coconutruben@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
ca1c3f354eb0a925742c2bac0473b79db1df241a	20-Sep-2016	Ruben Rodriguez Buchillon <coconutruben@chromium.org>	power_LoadTest: Extracting page-load-time information into keyvals Measure an upper-bound on page-load time during power load test, and store in keyvals. Measurement starts right before we update tab to new url, and ends after the tab reports that loading is done. BUG=None TEST=power_LoadTest information found in keyvals: INVALID_ext_ms_page_load_time_max{perf}=2515 INVALID_ext_ms_page_load_time_mean{perf}=1264.63636364 INVALID_ext_ms_page_load_time_min{perf}=87 INVALID_ext_ms_page_load_time_std{perf}=791.896431787 usually without the INVALID ;) information found in logging.debug: 09/20 10:55:11.191 DEBUG\| power_LoadTest:0737\| The 5 slowest page-load-times are: http://www.zedo.com w/ 2735 ms http://www.att.com w/ 2537 ms http://www.chase.com w/ 2522 ms http://www.amazon.com w/ 2395 ms http://www.google.com w/ 2276 ms Change-Id: I57e8895874c8b34dbfad80f79f490a1b3c3cd966 Reviewed-on: https://chromium-review.googlesource.com/387170 Commit-Ready: Ruben Rodriguez Buchillon <coconutruben@chromium.org> Tested-by: Ruben Rodriguez Buchillon <coconutruben@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
7c5ed505418980be00d6f5770ec6e5aa67b059ff	13-Sep-2016	Ruben Rodriguez Buchillon <coconutruben@chromium.org>	power_LoadTest: Added mechanism to track time/url of successful and failed loads Extension script records on top of current success/failure mechanism url, timestamp, and load success/failure. Script puts this into the debug logging, but keeps it away from the keyvals. BUG=chromium:642383 TEST=power_LoadTest load success: 09/15 15:25:04.763 DEBUG\| power_LoadTest:0682\| [extension] @ loop_0 15:16:29:514 [load success] http://www.microsoft.com load failure: 09/15 15:25:04.765 DEBUG\| power_LoadTest:0682\| [extension] @ loop_0 15:16:41:36 [load failure] http://www.myspace.com load failure details: 09/15 15:25:04.719 DEBUG\| power_LoadTest:0682\| [extension] @ loop_0 15:19:51:356 [load failure details] http://www.twitter.com 15:19:48:437 \| [response code] 200 \| [url] http://www.shoplocal.com/static/common/img/favicon.ico\| \| [status line] HTTP/1.1 200 OK 15:19:48:891 \| [response code] 200 \| [url] https://abs.twimg.com/a/1473752312/css/t1/twitter_more_2.bundle.css\| \| [status line] HTTP/1.1 200 OK [...] 15:19:48:896 \| [response code] 200 \| [url] https://abs.twimg.com/a/1473752312/css/t1/twitter_more_1.bundle.css\| \| [status line] HTTP/1.1 200 OK Change-Id: I49ab90f20fb872f77351083ca5234c4f3a67de44 Reviewed-on: https://chromium-review.googlesource.com/384338 Tested-by: Ruben Rodriguez Buchillon <coconutruben@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> Commit-Queue: Ruben Rodriguez Buchillon <coconutruben@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
6083c7b520ddfdbb524baf626d5715013be8dbeb	30-Aug-2016	Ravi Chandra Sadineni <ravisadineni@chromium.org>	Support HMP for CPUFreqStats/CPUIdleStats BUG=chrome-os-partner:56397 TEST=test_that -b elm 100.96.48.52 power_Idle Now the key value pairs are percent_cpufreq_0_1_1105000_time percent_cpufreq_2_3_1001000_time percent_cpuidle_0_1_C0_time percent_cpuidle_2_3_C0_time Change-Id: Ib8da3d2daa67d7333522289f380442f6ee1a8fb5 Reviewed-on: https://chromium-review.googlesource.com/377683 Commit-Ready: Ravi Chandra Sadineni <ravisadineni@chromium.org> Tested-by: Ravi Chandra Sadineni <ravisadineni@chromium.org> Reviewed-by: Ravi Chandra Sadineni <ravisadineni@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
e2ad5763d4db741f6ffdcb89479a97c6fbd628f5	01-Jun-2016	Todd Broch <tbroch@chromium.org>	power_LoadTest: publish percent_cpuidle_C0_time perf value. CPU C0 utilization can provide useful metric for tracking battery life regressions in the absence of reliable battery drain data. Lets track it. BUG=chromium:616153 TEST=test_that power_LoadTest.fast_gaia Contents of results-chart.json, { "percent_cpuidle_C0_time": { "summary": { "units": "percent", "type": "scalar", "value": 43.173375902954845, "improvement_direction": "down" } } Change-Id: I8615a1a872ae2bedde5ed059223c064765163d85 Reviewed-on: https://chromium-review.googlesource.com/349370 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Sameer Nanda <snanda@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
67cdc80fd1d8fcc604332ad9f3d03feff3bab5d8	03-Jun-2016	Todd Broch <tbroch@chromium.org>	power_utils.py: create DisplayPanelSelfRefresh class. Lets move this useful functionality to a utility class in power_utils so that other tests might take advantage of it. BUG=chrome-os-partner:53976 TEST=test_that power_LoadTest.fast See PSR residency keyval =~ 35% Change-Id: I3be07628afeb0fcc4866cd4ca2ee8037f744683d Reviewed-on: https://chromium-review.googlesource.com/349661 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
e392076b2a0182ba2593d529dc0e01dfbcb2a5b6	03-Jun-2016	Todd Broch <tbroch@chromium.org>	power_LoadTest: prefix PSR residency keyval with percent. BUG=chrome-os-partner:53976 TEST=none Change-Id: I415e3228419e67c2da4e8c65fb42ac5265f27802 Reviewed-on: https://chromium-review.googlesource.com/349660 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
c9c0fe619af775caca6a67928c77a00c84eb1a22	27-Apr-2016	Todd Broch <tbroch@chromium.org>	power_LoadTest: check AC power applied during test. As this is a long running test we should periodically check whether we're on AC and if ac_ok is false fail with same exception. BUG=none TEST=test_that $dut power_LoadTest.1hour Start test without AC, then plug in AC and see exception raised. Change-Id: I2490feb641e04dec0ffbe5dd24522b5659658e37 Reviewed-on: https://chromium-review.googlesource.com/341071 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Sameer Nanda <snanda@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
f77f59bfb5bcb0c3ea6582502a493db8bd1de4f9	15-Apr-2016	Todd Broch <tbroch@chromium.org>	power_LoadTest: Allow fake login if GAIA login fails. BUG=chrome-os-partner:52404 TEST=below test_that $dut power_LoadTest.fast - test succeeds - keyval username{perf}=GUEST is written - all key names prepended with INVALID_ Modify control.fast so gaia_login=True and run on R50 - in addition to above see warning 'Unable to use GAIA acct powerloadtest@gmail.com. Using GUEST instead.' Change-Id: I1f9cfb7be36f8f2c511e99ef79d3779fb75eb082 Reviewed-on: https://chromium-review.googlesource.com/339231 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Sameer Nanda <snanda@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
85dad304a61986ebeff63f749b5b307d152d74a5	27-Apr-2016	Ravi Chandra Sadineni <ravisadineni@chromium.org>	Adjusting kb backlight based on ALS and Hover. BUG=chromium:604959 CQ-DEPEND=CL:341504, CL:341497, CL:340640, CL:340990 TEST=ran test_that power_LoadTest on pixel2 and passed. Change-Id: I0cf93abe047a256b6c69d5bf70cdf68ff33956a0 Reviewed-on: https://chromium-review.googlesource.com/340881 Commit-Ready: Ravi Chandra Sadineni <ravisadineni@chromium.org> Tested-by: Ravi Chandra Sadineni <ravisadineni@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
4d4f45772fd8e708e019e31fc41f0cfa9d764919	21-Apr-2016	Todd Broch <tbroch@chromium.org>	power_LoadTest: skip test for devices without batteries. BUG=chromium:604793 TEST=run on test on chromebox and see if fail w/ TestNAError: Device designed without battery. Skipping test. Change-Id: I7d92b6a8bbf661a9500d2790a9380a31804208ea Reviewed-on: https://chromium-review.googlesource.com/340001 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Sameer Nanda <snanda@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
0d61ffb567a6d0e55c332b0ab1e05caf01000b77	23-Feb-2015	Eric Caruso <ejcaruso@chromium.org>	power_LoadTest: log memory bandwidth Dumps human-readable memory bandwidth logs into the .DEBUG file. This might be useful for debugging power issues since these values can act as a proxy for processor activity. BUG=None TEST=run power_LoadTest.fast with log_mem_bandwidth=True and inspect DEBUG logs Change-Id: Ibed423f4a8a582dd775723556c3b96f000bc535d Reviewed-on: https://chromium-review.googlesource.com/252271 Commit-Ready: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
d996e409a3debba138a3ed9523d6a2cad49b210a	05-Nov-2015	Todd Broch <tbroch@chromium.org>	power_LoadTest: Increase wifi config timeout after failure to connect. Runs in lab environment occasionally fail during final step, configuration, when connecting to wifi. CL increasing the timeout for configuration in hopes that AP just hasn't been given enough time to complete that step. It also adds logging to expose timeout values and failure string which is returned. BUG=chromium:337028 TEST=pylint passes Change-Id: I711783522451ac13aba227641695740d054a8129 Reviewed-on: https://chromium-review.googlesource.com/310986 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Derek Basehore <dbasehore@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
deac9bc81f75261120c42458da2c26e08987117f	28-Oct-2015	Derek Basehore <dbasehore@chromium.org>	power_LoadTest: Open trap window for auto loaded tabs There's a tab that opens on first login for Chromebooks for free offers. Since every login for power_LoadTest is a first login (since the state is cleared), open a window to catch that tab (and any others) which will be closed by the test later. BUG=None TEST=run power_LoadTest.1hour Check that there are only 5 tabs in the background window Change-Id: I650f636e23435c4f8e9a26b09a39ef378cd94068 Reviewed-on: https://chromium-review.googlesource.com/309543 Commit-Ready: Derek Basehore <dbasehore@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
172ecb7f5a6bbda741799444237a9be4ee21518b	03-Jun-2015	Ed Baker <edward.baker@intel.com>	Consolidate client downloads Downloading files can be consolidated using file_utils. This is part of a series of changes addressing client tests behind a proxy. BUG=chromium:496264 TEST=`test_that ${DUT_IP} firmware_TouchMTB \ login_GaiaLogin \ platform_Crouton \ video_ChromeRTCHWDecodeUsed \ video_ChromeRTCHWEncodeUsed \ video_HangoutHardwarePerf.vp8 \ video_PlaybackPerf.vp8 \ video_VDAPerf \ video_VEAPerf.vp8 \ video_VideoEncodeAccelerator.vp8 \ video_WebRtcPerf` TEST=`test_that ${DUT_IP} power_LoadTest` Change-Id: I98e78dd063294dde5530e32154b2f98c1ebe9a9e Reviewed-on: https://chromium-review.googlesource.com/275030 Commit-Ready: Edward Baker <edward.baker@intel.com> Tested-by: Edward Baker <edward.baker@intel.com> Reviewed-by: Rohit Makasana <rohitbm@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
fd456804cb8f90f43589f440e0a12c3a7fc7c9d4	30-Jul-2015	Derek Basehore <dbasehore@chromium.org>	power_LoadTest: set extension params directly This has the autotest set the extension params by executing JavaScript through the python object. This fixes issues with & and + in urls for the tasks list. BUG=chromium:515240 TEST=run power_LoadTest Change-Id: I1c8889fa67822e18d7c80f20b38ac5aaa0f94c6d Reviewed-on: https://chromium-review.googlesource.com/289668 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/power_LoadTest.py
99c242a22b990e59cac306efa392a2f0f3215bc4	10-Apr-2015	Derek Basehore <dbasehore@chromium.org>	Store powerloadtest password on chromium.org This fetches the password for powerloadtest from chromium.org so it's simpler to change the password (no merging back to many branches). BUG=chrome-os-partner:38926 TEST=run power_LoadTest and login_GaiaLogin Change-Id: I2756b9df26912a6d2bf0c7c99e0459f14b03344c Reviewed-on: https://chromium-review.googlesource.com/265250 Reviewed-by: Achuith Bhandarkar <achuith@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Sameer Nanda <snanda@chromium.org> Commit-Queue: Derek Basehore <dbasehore@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
e26cce9fe237a268bff9208edf37fef353ce7f52	08-Apr-2015	Derek Basehore <dbasehore@chromium.org>	Update power_LoadTest password This updates the password for power_LoadTest and login_GaiaLogin BUG=chromium:475198 TEST=run power_LoadTest and login_GaiaLogin Change-Id: I70b1a6d64f666534ff3b8a8cc6897918707ba9f5 Reviewed-on: https://chromium-review.googlesource.com/264785 Reviewed-by: Sameer Nanda <snanda@chromium.org> Commit-Queue: Derek Basehore <dbasehore@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
61b032031e418fece0430cf13bd84fff239ac603	23-Mar-2015	Eric Caruso <ejcaruso@chromium.org>	power_LoadTest: only use powerlogger numbers for short runs Charge numbers are accurate for full runs and less prone to battery statistics being misreported, so we should use those if we're not doing a one-hour run. BUG=chromium:469812 TEST=run short power_LoadTest with 1 loop and 2 loops and check that powerlogger is used for 1 loop, but charge is used for 2 loops Change-Id: Ibfbae0597b21ba3ee8c3b6f8049254a08720b707 Reviewed-on: https://chromium-review.googlesource.com/261946 Reviewed-by: Derek Basehore <dbasehore@chromium.org> Commit-Queue: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
2633eef2994f6d798f2c22000c006063bee1ae85	18-Feb-2015	Eric Caruso <ejcaruso@chromium.org>	power_LoadTest: improve battery life estimate with large voltage swings Currently, battery life estimation occurs by taking the percentage of full charge that discharged over the course of the run and using that as a scaling factor. However, this means one-hour runs with a high battery level will overshoot the actual battery life significantly, since the voltage coming from the battery is high and thus the current lower than normal at this point. Runs that occur with very low battery may similarly have lower voltage and thus draw more current. This means the battery life prediction is fairly useless for a one-hour run. powerd estimates battery life differently, by taking the full charge and multiplying by the design voltage to get the maximum energy stored, and then dividing this by a moving average of power draw. This is a much more accurate way to gauge battery life as experimentally found by snanda@. However, the w_energy_rate and wh_energy_used keyvals are calculated from the design voltage and the charge, meaning they are subject to the same inaccuracy we are trying to avoid by using energy instead of charge in the first place. This CL calculates energy used from the power logger, which appears to be much more accurate in gauging the power draw. BUG=None TEST=Ran PLT with full-ish battery, verified that estimates were +-5% compared to calculations using external measurements of power draw Change-Id: I572ebbb760e27ab18dd92d1cb7e7d72ba0a618e4 Reviewed-on: https://chromium-review.googlesource.com/250629 Reviewed-by: Sameer Nanda <snanda@chromium.org> Commit-Queue: Eric Caruso <ejcaruso@chromium.org> Trybot-Ready: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
1bc91d6b5e86fe30b2c1b6bb74262c57c1ec7e35	05-Jan-2015	Christopher Grant <cjgrant@google.com>	Cut a tie between power_LoadTest and backchannel power_LoadTest uses backchannel, but also made use of a questionable backchannel utility function to check whether a network interface is up. This is the only use of that utility function, and this is a step towards removing the function from backchannel. BUG=chrome-os-partner:35127 TEST=Being tested by test owners. CQ-DEPEND=CL:236942 Change-Id: I812e4edb454216329d1e7b3242723d1d83167c2e Reviewed-on: https://chromium-review.googlesource.com/238370 Trybot-Ready: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> Commit-Queue: Christopher Grant <cjgrant@chromium.org> Tested-by: Christopher Grant <cjgrant@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
c2e7bbbdc18d080e2eabd90fa158404961556087	15-Dec-2014	Eric Caruso <ejcaruso@chromium.org>	power_LoadTest: fix test for boards without psr If the board does not support PSR, we fail since we can't open the PSR status file. Instead, we should just note the error and continue as usual. BUG=chromium:442125 TEST=test_that Change-Id: I527a10b2331a8106fd610de5ea63061f8496fb44 Reviewed-on: https://chromium-review.googlesource.com/235802 Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> Commit-Queue: Eric Caruso <ejcaruso@chromium.org> Trybot-Ready: Eric Caruso <ejcaruso@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
edfd5ba0e55670be04143d919b7d559b56a9bf35	12-Dec-2014	Eric Caruso <ejcaruso@chromium.org>	power_LoadTest: add keyval for PSR residency If the PSR performance counter exists, we can use it to track what percentage of the test we spent in PSR. If this number is unusually low, we may be drawing more power than necessary. BUG=chromium:441514 TEST=test_that, check keyval against log readings Change-Id: Ifdea795883655db4133e843fe1cfa25ca2501e9d Reviewed-on: https://chromium-review.googlesource.com/234873 Trybot-Ready: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Sameer Nanda <snanda@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> Commit-Queue: Eric Caruso <ejcaruso@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
225dd2cccba21b0a9ebd40404a6630704a243d82	25-Sep-2014	Todd Broch <tbroch@chromium.org>	power_LoadTest: Bump password. BUG=chrome-os-partner:29849 TEST=manual, login to account. Change-Id: I44a58867689a811c00380845b43840bb9569fb1f Reviewed-on: https://chromium-review.googlesource.com/219991 Commit-Queue: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Sameer Nanda <snanda@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
41acbf89080501db1b554c6919e1e0b3593585ff	12-Jul-2014	Derek Basehore <dbasehore@chromium.org>	Add close method for Chrome This adds a close method for the Chrome class and calls it during cleanup in power_LoadTest. This makes power_LoadTest close Chrome when it finishes. BUG=chromium:393027 TEST=run power_LoadTest Change-Id: Ic3511a3c1908040a5b90e99645980b4bd35a9a68 Reviewed-on: https://chromium-review.googlesource.com/207688 Reviewed-by: Achuith Bhandarkar <achuith@chromium.org> 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/power_LoadTest.py
95a4581239a1ab8cfabae0e50de7d6743fb71a61	23-Jun-2014	Todd Broch <tbroch@chromium.org>	power_LoadTest: Bump pswd. BUG=chrome-os-partner:29849 TEST=manual, login to account. Change-Id: Ic3366c4c78d1e11b3278653b992d242efc5eea88 Reviewed-on: https://chromium-review.googlesource.com/204979 Reviewed-by: Sameer Nanda <snanda@chromium.org> Commit-Queue: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
5cfd7fab4966bf402c4073a41707c31b26cb8c5f	13-Jun-2014	Achuith Bhandarkar <achuith@chromium.org>	Minor cleanup of power_LoadTest. Remove creds. Remove unused cros_ui methods. BUG=None TEST=power_LoadTest Change-Id: Ic67d1b0a1e3b10db2b52dda78ea26a0238038b02 Reviewed-on: https://chromium-review.googlesource.com/203654 Reviewed-by: Derek Basehore <dbasehore@chromium.org> Commit-Queue: Achuith Bhandarkar <achuith@chromium.org> Tested-by: Achuith Bhandarkar <achuith@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
a8d49fffc08e05a5cccaa5821c84bd4ca86768a8	03-Jun-2014	Todd Broch <tbroch@chromium.org>	Add separator for ext_ keyvals to discern loop data better. BUG=chromium:373848 TEST=run power_LoadTest (two loops) See ext_ keyvals with '_' ext_audio_failed_loads{perf}=0_0 ext_audio_successful_loads{perf}=1_1 ext_docs_failed_loads{perf}=0_0 ext_docs_successful_loads{perf}=5_5 ext_email_failed_loads{perf}=0_0 ext_email_successful_loads{perf}=3_3 ext_status{perf}=good_good ext_web_failed_loads{perf}=0_0 ext_web_successful_loads{perf}=28_29 Change-Id: I9911015f52611f22a14d98c80949d560ef1fb68c Reviewed-on: https://chromium-review.googlesource.com/202452 Reviewed-by: Sameer Nanda <snanda@chromium.org> Commit-Queue: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
d16f1daab3a354b637065b99dbc31809ce5674dd	02-Jun-2014	Alex Miller <milleral@chromium.org>	Move service_stopper to initialize and cleanup for power tests. TEST=None BUG=None Change-Id: I61ab4493c689a0249503de03963e97d649e71dce Reviewed-on: https://chromium-review.googlesource.com/202344 Tested-by: Alex Miller <milleral@chromium.org> Reviewed-by: Derek Basehore <dbasehore@chromium.org> Commit-Queue: Alex Miller <milleral@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
04be2bd5e4666a5c253e9c30ab20555e04286032	08-May-2014	Ilja H. Friedel <ihf@chromium.org>	Autotest: Change logging.warn() to logging.warning(). logging.warn() is deprecated. See http://bugs.python.org/issue13235 Substitution was performed via ~/cros/src/third_party/autotest/files$ find ./ -type f \| xargs sed -i 's/logging.warn(/logging.warning(/' BUG=None. TEST=There should be one-- and preferably only one --obvious way to do it. Change-Id: Ie5665743121a49f7fbd5d1f47896a7c65e87e489 Reviewed-on: https://chromium-review.googlesource.com/198793 Commit-Queue: Ilja Friedel <ihf@chromium.org> Tested-by: Ilja Friedel <ihf@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
664bad8943c04684b1181e53dc0e58d598733c55	06-May-2014	Derek Basehore <dbasehore@chromium.org>	power_LoadTest: Work around extension loading twice This works around Chrome loading the extension for OOBE and after login by making the extension not automatically start on load. The icon can still be clicked to start the extension though. Instead, this relies on power_LoadTest.py to start the test by executing a javascript function for the extension. BUG=chrome-os-partner:27981 TEST=run power_LoadTest check that only one set of windows opens Change-Id: Ib10ce757b3fdabca4604f148374f80993fc34e85 Reviewed-on: https://chromium-review.googlesource.com/198278 Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Achuith Bhandarkar <achuith@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Sameer Nanda <snanda@chromium.org> Commit-Queue: Derek Basehore <dbasehore@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
19b22d991c000510e91aca1b7bce6c57b9a63a15	01-May-2014	Todd Broch <tbroch@chromium.org>	Don't try to publish minutes_battery_life keyval unless it exists. This commit, 87445df power_LoadTest: Add perf reporting Added reporting of minutes_battery_life to perf while this commit, 3932cc3 power_LoadTest: Allow running on AC. Made it possible to no longer have battery discharge and therefore not calculate minutes_battery_life keyval. Auto-merge introduced bug which this now fixes. BUG=none TEST=run power_LoadTest on AC and it finishes successfully without throwing error Unhandled KeyError: 'minutes_battery_life' Change-Id: I1e4dbc2933de2b39981e30447e58ca4167a6bc14 Reviewed-on: https://chromium-review.googlesource.com/197782 Reviewed-by: Derek Basehore <dbasehore@chromium.org> Commit-Queue: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
3932cc39076c41847e4b8201abb225528b4b815e	23-Apr-2014	Todd Broch <tbroch@chromium.org>	power_LoadTest: Allow running on AC. Test is useful benchmark regardless of whether determining battery life so allow it to be run if AC is connected. Change adds keyval 'on_ac' and qualifies battery life calculations to avoid div-by-zero errors to enable/identify this mode. BUG=none TEST=run power_LoadTest 1. with ac_ok=True for init - Test passes, b_ac_on == True 2. with ac_ok=False for init - Test fails with message ' ERROR: Running on AC power. Please remove AC power cable. Change-Id: If38f8a52063deed036703494403447fbac05953e Reviewed-on: https://chromium-review.googlesource.com/196524 Reviewed-by: Sameer Nanda <snanda@chromium.org> Commit-Queue: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
87445df0c3a04de57e214267d5131e37148c76e4	19-Apr-2014	Derek Basehore <dbasehore@chromium.org>	power_LoadTest: Add perf reporting This just reports the estimated battery life for the end of the 1 hour test from the lab. BUG=chromium:304723 TEST=power_LoadTest Change-Id: I494642aa450316435ff911099b3029269a14545c Reviewed-on: https://chromium-review.googlesource.com/195703 Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> Commit-Queue: Derek Basehore <dbasehore@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
0ecaa5c74b6943368ba80cedca2259931f51426a	03-Apr-2014	Derek Basehore <dbasehore@chromium.org>	Move power_LoadTest over to Telemetry This moves power_LoadTest over to Telemetry from PyAuto. Telemetry will use a full screen window if it is the default for your window size, where PyAuto did not. This should not result in a major difference in power though. TEST=power_LoadTest BUG=chromium:337029 Change-Id: I1bfc996439c1c8ad1b467539fb51e49346e70b7d Reviewed-on: https://chromium-review.googlesource.com/193054 Reviewed-by: Derek Basehore <dbasehore@chromium.org> Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org> Commit-Queue: Derek Basehore <dbasehore@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
fd4caad0dadc545b7458c16c2340fecfbfd1fe40	24-Mar-2014	Todd Broch <tbroch@chromium.org>	power_LoadTest: fixup extension status reporting. Re-locate the http server code to gather extension statistics for reporting them to results such that extension is active. Also removed manual xsetting that appears to no longer be necessary. BUG=chromium:305892 TEST=run power_LoadTest with loop_time=300, loop=1 and it looks correct and publishes extension status to keyval as: ext_audio_failed_loads{perf}=0 ext_audio_successful_loads{perf}=1 ext_docs_failed_loads{perf}=0 ext_docs_successful_loads{perf}=6 ext_email_failed_loads{perf}=0 ext_email_successful_loads{perf}=3 ext_status{perf}=good ext_web_failed_loads{perf}=0 ext_web_successful_loads{perf}=36 Change-Id: Ieed3ad5263545fe63a428c3a7ca5c41d26080e87 Reviewed-on: https://chromium-review.googlesource.com/191280 Reviewed-by: Derek Basehore <dbasehore@chromium.org> Commit-Queue: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
1ce77c09e27cd4dbd0cfbdb5b72e494d850961d5	21-Feb-2014	Sameer Nanda <snanda@chromium.org>	power_LoadTest: update credentials Update credentials to match new account settings. BUG=none TEST=run power_LoadTest and verify that it is able to log in successfully as part of the test run. Change-Id: If14af7f5ed6228e5240b3f34bd2d856874297b52 Reviewed-on: https://chromium-review.googlesource.com/187388 Reviewed-by: Bryan Freed <bfreed@chromium.org> Commit-Queue: Sameer Nanda <snanda@chromium.org> Tested-by: Sameer Nanda <snanda@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py
f10a3198906c17a539c830e1263e6efb0a3db7b2	11-Jan-2014	Derek Basehore <dbasehore@chromium.org>	power_LoadTest: Forget wifi AP at the end of the test In the case that we force a connection to a wifi AP, forget all wifi connections at the beginning and end of the test. This is intended to help reduce wifi congestion in the test lab. BUG=chromium:297830 TEST=run power_daily suite in the lab Change-Id: I259e9c9abfda889196370f2f70605d7ec2d76ef3 Reviewed-on: https://chromium-review.googlesource.com/182185 Tested-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Christopher Wiley <wiley@chromium.org> Commit-Queue: Derek Basehore <dbasehore@chromium.org> /external/autotest/client/site_tests/power_LoadTest/power_LoadTest.py