diff options
| author |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-04-06 17:19:05 +0100 |
|---|---|---|
| committer |   Ross Burton <ross.burton@intel.com> | 2013-04-23 11:07:45 +0100 |
| commit | f03a0eb83be9acb1b418ff4632611a32bd69bf6c (patch) | |
| tree | e14561d9c5116de75974ffeb2c29498d47b0f88a | |
| parent | 1b702e0c546beaf3b0ffef0c8e57ea254aef4996 (diff) | |
| download | openembedded-core-f03a0eb83be9acb1b418ff4632611a32bd69bf6c.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>
| -rwxr-xr-x | scripts/qemuimage-tests/sanity/boot | 2 |
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} |