openembedded-core.git/scripts/qemuimage-tests/sanity/boot, branch master Mirror of openembedded-core classes/imagetest-qemu: remove old image testing class 2013-09-20T11:14:32+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2013-09-19T12:18:06+00:00 d469c92394a1a95ae7a45b8b80dc4c2918e0e9a6 This has now been superseded by testimage. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> 
This has now been superseded by testimage.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
qemuimage-tests/sanity/boot: Increase timeout 2013-04-06T16:19:05+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-04-06T16:19:05+00:00 331118a253e26821011a31ca9087611ea58a18b8 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> 
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>
Replace POKYBASE with COREBASE 2011-04-20T17:07:30+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-04-20T15:56:03+00:00 607a7657715f6fcba467a4e55ba64f41f4e13a15 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rename poky-qemu to runqemu 2011-04-20T15:44:10+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-04-20T15:44:10+00:00 7687d91f73f4a116593315b3b1488ac3f0904905 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
imagetest-qemu: Add sanity test cases for scp/shutdown in target 2010-11-15T05:08:22+00:00 Jiajun Xu jiajun.xu@intel.com 2010-11-10T14:58:52+00:00 d64c7ae88ca29def7dd2869acaa0e2ec047bd153 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> 
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>
imagetest-qemu: Add test case for dmesg check in target 2010-11-10T13:09:22+00:00 Jiajun Xu jiajun.xu@intel.com 2010-10-29T17:03:22+00:00 12a861359a3413ded52174c814e8653c56caee17 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> 
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>
Enable build dir outside of the poky directory 2010-07-21T14:39:53+00:00 Joshua Lock josh@linux.intel.com 2010-07-21T13:55:39+00:00 971907567cff64e74f21d349d6751dadc8c09827 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> 
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>
test: add automation framework and sanitytest 2010-07-15T11:48:25+00:00 Jiajun Xu jiajun.xu@intel.com 2010-07-07T18:06:58+00:00 fd1d661b391dfad1edaac937a17c1165f635031a 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> 
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>