dark_resume_utils: stop then start powerd instead of restart powerd
In some cases powerd isn't running before the test starts, 'restart
powerd' will fail with command execution error. Use 'stop powerd; start
powerd' instead to prevent error in this case.
BUG=chrome-os-partner:43894
TEST=none
Change-Id: I2b3feab9a2ed7c7fa332d2ba9b6914600bad46d8
Reviewed-on: https://chromium-review.googlesource.com/331885
Commit-Ready: Wei-Ning Huang <wnhuang@chromium.org>
Tested-by: Wei-Ning Huang <wnhuang@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
diff --git a/server/cros/dark_resume_utils.py b/server/cros/dark_resume_utils.py
index 8897bbb..a7d12e2 100644
--- a/server/cros/dark_resume_utils.py
+++ b/server/cros/dark_resume_utils.py
@@ -103,7 +103,7 @@
host.run('mount --bind %s %s' % (TMP_POWER_DIR, POWER_DIR))
logging.debug('Restarting powerd with new settings')
- host.run('restart powerd')
+ host.run('stop powerd; start powerd')
logging.debug('Starting XMLRPC session to watch for dark resumes')
self._client_proxy = self._get_xmlrpc_proxy()
@@ -118,7 +118,7 @@
self._host.run('umount %s' % POWER_DIR)
logging.debug('Restarting powerd to revert to old settings')
- self._host.run('restart powerd')
+ self._host.run('stop powerd; start powerd')
def suspend(self):