recover_duts: increase polling frequency
This is an architectural change: the "hook" will check
it's state and run exactly once if it's allowed.
Thus we need to check more often.
90 seconds is about 2x longer than it should ever take to have a
working network (wired ethernet). My experience is a USB NIC will
be up and working within 20 seconds of power on. But on a bad day it
might take 15-20 seconds to load the NIC driver module and then dhcpcd
could timeout after 30 seconds. I don't know if shill is retrying
anything and I don't expect that is matters since dhcpcd retries.
BUG=chromium:677572
TEST=Copy recovery_duts to DUT and reboot.
Manually verify hook is invoked every minute after
LONG_REBOOT_DELAY has expired.
Change-Id: I3da58c2378269ff1e10fb7e024dd2d4ec559eeb3
Reviewed-on: https://chromium-review.googlesource.com/704256
Commit-Ready: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@google.com>
Reviewed-by: Grant Grundler <grundler@chromium.org>
diff --git a/recover_duts/recover_duts.py b/recover_duts/recover_duts.py
index ffaac0f..a43ea85 100755
--- a/recover_duts/recover_duts.py
+++ b/recover_duts/recover_duts.py
@@ -23,8 +23,8 @@
LOGGING_SUBDIR = '/var/log/recover_duts'
LOG_FILENAME = 'recover_duts.log'
LOGGING_FORMAT = '%(asctime)s - %(levelname)s - %(message)s'
-LONG_REBOOT_DELAY = 300
-SLEEP_DELAY = 600
+LONG_REBOOT_DELAY = 90
+SLEEP_DELAY = 60
LOG_FILE_BACKUP_COUNT = 10
LOG_FILE_SIZE = 1024 * 5000 # 5000 KB
