From f03a0eb83be9acb1b418ff4632611a32bd69bf6c Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Sat, 6 Apr 2013 17:19:05 +0100 Subject: qemuimage-tests/sanity/boot: Increase timeout As we've increased the parallelisation on the build servers, we've started to see core-image-minimal sanity test boot failures where the network never comes up. We don't see those failures for core-image-sato, its always minimal. Looking at the results, it can take ~100 seconds for the network to come up, even on the sato images if the machine has a high load. The timeout for the boot test is only 120 seconds compared to 400 on every other test. This change makes the timeout equal for all the tests at 400 seconds in the hope that the load on the autobuilder is causing the sanity tests to run slowly and hence triggering the false negatives. Signed-off-by: Richard Purdie --- scripts/qemuimage-tests/sanity/boot | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/qemuimage-tests/sanity/boot b/scripts/qemuimage-tests/sanity/boot index cf8aafbc50..5a8c01c9ac 100755 --- a/scripts/qemuimage-tests/sanity/boot +++ b/scripts/qemuimage-tests/sanity/boot @@ -11,7 +11,7 @@ # . $COREBASE/scripts/qemuimage-testlib -TIMEOUT=120 +TIMEOUT=400 # Start qemu and check its network Test_Create_Qemu ${TIMEOUT} -- cgit 1.2.3-korg