aboutsummaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-06 17:19:05 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-06 17:19:05 +0100
commit331118a253e26821011a31ca9087611ea58a18b8 (patch)
tree45ea5533a38608c524a0fa167ae8fac9629b792d /scripts
parentf0aa69296f4c1d4214f9dbea236b0ed330b8154b (diff)
downloadopenembedded-core-contrib-331118a253e26821011a31ca9087611ea58a18b8.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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts')
-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 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}