summaryrefslogtreecommitdiff
path: root/scripts/qemuimage-tests/sanity/boot
AgeCommit message (Collapse)AuthorFiles
2013-09-20classes/imagetest-qemu: remove old image testing classPaul Eggleton1
This has now been superseded by testimage. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-04-06qemuimage-tests/sanity/boot: Increase timeoutRichard Purdie1
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>
2011-04-20Replace POKYBASE with COREBASERichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20Rename poky-qemu to runqemuRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2010-11-14imagetest-qemu: Add sanity test cases for scp/shutdown in targetJiajun Xu1
scp test is to check if file copying via network work or not in target. shutdown test is to check if target can be poweroff with qemu process off. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2010-11-10imagetest-qemu: Add test case for dmesg check in targetJiajun Xu1
Add a test case for error log check with command dmesg in target. The case introduces a new folder in target, "/opt/test", which holds test scripts running in target. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2010-07-21Enable build dir outside of the poky directoryJoshua Lock1
You need to first set up the build directory by sourcing the poky build script, after that builds can be run in that directory so long as bitbake is in $PATH removing the need to source the init script for each build. i.e: $ . poky-init-build-env ~/my-build $ bitbake some-image <<later, in a different shell>> $ cd ~/my-build $ export PATH=/path/to/bitbake/bin:$PATH $ bitbake an-image This patch also removes use of OEROOT in recipes, etc. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2010-07-15test: add automation framework and sanitytestJiajun Xu1
Automation test is disabled by default. User need set TESTCLASS to qemu in conf/local.conf and run bitbake command "bitbake poky-image-xxx" or "bitbake poky-image-xxx -c qemuimagetest" to trigger it. Currently only the sanity test with two testcases are added. To run the test, user need prepare a testing environment: 1) "expect" should be installed on system 2) NOPASSWD should be set for user to run bitbake Signed-off-by Jiajun Xu <jiajun.xu@intel.com>