Increase reboot timeout to 120 seconds.
The "reboot timeout" includes more than the time from power on to
login screen visible. It must also include some time spent during
shutdown (after sshd is down, but before the system has entered
firmware for reboot), and after boot (after the login screen is
visible, but before sshd is able to accept connections). Moreover,
new platforms are coming that boot substantially slower than
existing platforms. These two factors meant that the reboot timeout
of 30 seconds was much too short.
The new default of 120 seconds is more than twice what is needed
for any known platform. A generous margin is provided because it is
generally preferable never to time out: Boot time testing can be
used to confirm that boot time hasn't regressed. In particular,
the short timeout was causing boot time tests to abort rather than
complete, making it hard to get accurate boot time measurements.
BUG=chromium-os:31748
TEST=platform_BootPerfServer
Change-Id: I9e59341ddcddfef2f266496bc8a6889a3ab5b446
Reviewed-on: https://gerrit.chromium.org/gerrit/34555
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
diff --git a/global_config.ini b/global_config.ini
index f669d4a..0daf078 100644
--- a/global_config.ini
+++ b/global_config.ini
@@ -100,7 +100,7 @@
wait_up_processes:
default_protection: NO_PROTECTION
# Time in seconds to wait for a machine to come back after reboot.
-default_reboot_timeout: 30
+default_reboot_timeout: 120
# Time in seconds to wait for a machine to go down prior to reboot.
wait_down_reboot_timeout: 30
# Time in seconds to wait before generating a warning if a host has not gone