summaryrefslogtreecommitdiffstats
path: root/scripts/qemuimage-tests/scenario/qemumips/core-image-sato
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-23 13:00:54 +0100
commit7f468c2247204548501d0291a03f554d93ed81dc (patch)
tree4e83b5c6fe65444d3ebb231341bd76241db8178f /scripts/qemuimage-tests/scenario/qemumips/core-image-sato
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>
Diffstat (limited to 'scripts/qemuimage-tests/scenario/qemumips/core-image-sato')
0 files changed, 0 insertions, 0 deletions