power: autotest: stop disabling powerd during tests |
|||||||
Issue descriptionWant to revisit which tests we disable powerd in during autotest. The daemon has typically been stopped to disable idle timeouts & allow manual control of backlights (kbd & panel). However this comes at a cost of not testing this daemon's impact on the system. At least for battery life tests, (LoadTest, Consumption, video_*Perf) tests we should keep the daemon running and instead alter behavior slightly. Panel backlight should be set to default levels accordingly by daemon as it should match result of get_powerd_initial_backlight_level which is the preferred alternative in absence of powerd. Need to evaluate and potentially add hooks in powerd to: - control keyboard backlight to fixed level (irrespective of things like ALS & hover) - disable idle timeouts - other things? Once those items above are done we should be able to leave powerd running for battery life tests.
,
Mar 11 2016
I think one of the problems here is that Chrome will try to interact with powerd if it's available. I would suggest using external policies to turn off idle timeouts, but Chrome sends external policies of its own, so it might stomp on our toes. We could add some JavaScript to the tests which will take a Chrome wake lock, and then Chrome will send an external policy with all idle timeouts disabled.
,
Mar 11 2016
powerd has an ignore_external_policy pref. Its meaning could be updated so that powerd still honors policies set via the set_power_policy tool. The keyboard backlight is probably the main thing that isn't covered right now, but it'd probably be easy to add a SetKeyboardBrightness D-Bus method for this.
,
Mar 11 2016
Right, I was worried about ignore_external_policy for that reason. We could also bind-mount a prefs directory that sets ignore_external_policy, disables all the idle timeouts, adds brightness prefs for non-ALS systems and brightness tables for ALS with one value (the same one as the non-ALS table). Restarting powerd at that point should do what we want.
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 9 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by tbroch@chromium.org
, Mar 11 2016Labels: OS-Chrome