summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-06 16:19:05 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-23 12:00:54 (GMT)
commit7f468c2247204548501d0291a03f554d93ed81dc (patch)
tree4e83b5c6fe65444d3ebb231341bd76241db8178f
parentf8b915128b202503f13a57ce8531781e251ff2d6 (diff)
downloadpoky-7f468c2247204548501d0291a03f554d93ed81dc.tar.gz
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. (From OE-Core rev: f03a0eb83be9acb1b418ff4632611a32bd69bf6c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rwxr-xr-xscripts/qemuimage-tests/sanity/boot2
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/qemuimage-tests/sanity/boot b/scripts/qemuimage-tests/sanity/boot
index cf8aafb..5a8c01c 100755
--- a/scripts/qemuimage-tests/sanity/boot
+++ b/scripts/qemuimage-tests/sanity/boot
@@ -11,7 +11,7 @@
11# 11#
12. $COREBASE/scripts/qemuimage-testlib 12. $COREBASE/scripts/qemuimage-testlib
13 13
14TIMEOUT=120 14TIMEOUT=400
15 15
16# Start qemu and check its network 16# Start qemu and check its network
17Test_Create_Qemu ${TIMEOUT} 17Test_Create_Qemu ${TIMEOUT}