[PATCH i-g-t 1/1] runner: Bump network ping deadline to 40 seconds

[Kamil Konieczny]

From: Peter Senna Tschudin <peter.senna at linux.intel.com>

Commit ddfde25f16ba ("runner: Add support for aborting on
network failure") introduced a 20 second deadline for the DUTs
network to recover after a suspend/resume cycle. If the network
isn't back up within that time, igt_runner aborts the test run
to save logs and prevent potential log loss from an imminent
power cycle.

External monitoring machine checks DUTs health and if it cannot
reach it over network for 60 seconds it will reboot DUT.

Although our CI system can be configured with a longer wait
time, extending it further would unnecessarily prolong tests in
cases of DUT hangs.

Bump the deadline to 40 seconds to prevent a premature igt_runner
abort.

Cc: Katarzyna Piecielska <katarzyna.piecielska at intel.com>
Cc: Ewelina Musial <ewelina.musial at intel.com>
Cc: Mateusz Grabski <mateusz.grabski at intel.com>
Cc: Konrad Brodzik <konrad.b.brodzik at intel.com>
Cc: Kamil Konieczny <kamil.konieczny at linux.intel.com>
Signed-off-by: Peter Senna Tschudin <peter.senna at linux.intel.com>
Acked-by: Ryszard Knop <ryszard.knop at intel.com>
---
 runner/executor.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/runner/executor.c b/runner/executor.c
index 999e7f719..2abb18732 100644
--- a/runner/executor.c
+++ b/runner/executor.c
@@ -218,11 +218,11 @@ static bool load_ping_config_from_env(void)
 
 /*
  * On some hosts, getting network back up after suspend takes
- * upwards of 10 seconds. 20 seconds should be enough to see
+ * upwards of 10 seconds. 40 seconds should be enough to see
  * if network comes back at all, and hopefully not too long to
  * make external monitoring freak out.
  */
-#define PING_ABORT_DEADLINE 20
+#define PING_ABORT_DEADLINE 40
 
 static bool can_ping(void)
 {
-- 
2.48.1