summaryrefslogtreecommitdiff
path: root/scripts/qemuimage-tests
AgeCommit message (Collapse)AuthorFiles
2013-04-09qemuimagetest/scenario: Move dmesg to end of test runRichard Purdie15
The dmesg test detects segfaults. This is useful information to have and if one occurs in one of the earlier tests, this can aid debugging. Move the dmesg test to the end of the list of tests so we gain the extra debug info in those cases. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
2013-04-05sanity/connman: when connman test fails, dump syslogRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-05connman_test.sh: show all processes when dumping psRoss Burton1
We know the grep failed because the error case is being executed, so don't do the grep again when attempting to help diagnose the problem, as seeing the full process list might be useful. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-19qemu-testlib: Add python helper and simplify shellRichard Purdie1
The current code has a race since it greps for *any* qemu process running, even if it isn't the one we started. This leads to some sanity tests potentially failing on machines where multiple sets of sanity tests are running. To resovle this and some other ugly code issues, add a python script to accurately walk the process tree and find the qemu process. We can then replace all the shell functions attempting this which happen to work in many cases but not all. Also clean up some of the error handling so its more legible. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-02qemuimage-tests/dmesg: Add exception for error message on qemuarm with 3.8 ↵Richard Purdie1
kernel With 3.8 kernels we get a harmless error message during kernel boot. For now we can ignore. This allows the tests to pass and ensures we can merge the 3.8 kernel. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-14Update sanity tests to use smart instead of zypperPaul Eggleton19
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10qemuimagetest: modifying the scenario file as per new test casesVeerabrahmam vr10
modified scenario files. Signed-off-by: veerabrahmam <veerabrahmamvr@huawei.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10qemuimagetest: add basic function to check syslogdVeerabrahmam vr2
one test case to check syslogd is executing on target. Signed-off-by: veerabrahmam <veerabrahmamvr@huawei.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10qemuimagetest: add basic function to check enough disk spaceVeerabrahmam vr2
one test case to check disk space availability. Signed-off-by: veerabrahmam <veerabrahmamvr@huawei.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10qemuimagetest: basic function to check bash existsVeerabrahmam vr2
one test case to check bash command availability on qemu target. Signed-off-by: veerabrahmam <veerabrahmamvr@huawei.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-11-18sanitytest: use different option for command ps from busybox and procpsJiajun Xu1
Current sanitytest use option -e for ps command, which only works for ps from procps. It fails if ps is provided by busybox. Add check to use different option for command from busybox and procps. [YOCTO #1756] Signed-off-by: Jiajun Xu <jiajun.xu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-04connman_test.sh: Rework for busybox 'ps'Tom Rini1
This script has two problems today. First, it does 'ps -ef cmd' in failure which real ps doesn't grok and busybox ps just ignores the argument on. Switch that to 'ps -ef'. Second, busybox ps -o doesn't understand cmd but does understand comm. Using comm lets us simplify the test logic as well, so switch to that. Signed-off-by: Tom Rini <tom_rini@mentor.com>
2011-06-24qemuimagetest: update cvs and iptables to newer version for toolchain testJiajun Xu1
The old versions of cvs and iptables may meet compile error under some architecture - cvs 1.11.23 fails on x86-64 host and iptables 1.4.9 fails on arm host. Update them to latest version could solve these build error. Meanwhile, 240s timeout is set for sudoku becasue 120s is not enough to finish compile. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-05-04qemuimagetest: Add executable permission to test scripts for toolchainJiajun Xu3
The file mode bits of toolchain test scripts is 644, which could not be executed by user. Fix the issue by adding executable permission(755) to all test scripts for toolchain test. Signed-off-by Jiajun Xu <jiajun.xu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-04qemuimagetest: Enable toolchain automation tests in qemuimagetestJiajun Xu8
Enable toolchain automation tests in qemuimagetest framework. 3 C/C++ test projects are added to test toolchain - cvs, iptables and sudoku-savant. User needs to set TEST_SCEN to "toolchain" in local.conf to enable tests. Test case will check if toolchain tarball exists under "${DEPLOY_DIR}/sdk". And it will extract toolchain tarball into /opt. It requires user to chown /opt to non-root user, who will run qemuimagetest. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-04-20Rename poky-image-* -> core-image-* and task-poky-* -> task-core-*Richard Purdie20
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20Replace POKYBASE with COREBASERichard Purdie10
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20Rename poky-qemu to runqemuRichard Purdie10
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-02-10qemuimagetest: Rename test scenario file from poky-image-sdk to ↵Jiajun Xu5
poky-image-sato-sdk Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-20qemuimagetest: Use same image during sanity testing instead of copying a new ↵Jiajun Xu24
image for each case To reduce the time on sanity testing, we remove variable SHARE_IMAGE and use a new variable TEST_SERIALIZE in local.conf. It is by default set to 1. Poky will copy and boot the to-be tested image for only once. It will not remove or kill the image and test cases will be serialized executed against the same image. If it is set to 0, image is always be copied for each cases, which takes much time. I had a experiment that latest qemuppc sato only takes 7 minutes to finish 9 sanity test cases, which takes more than 20 minutes before. I also removed sanity case "boot" from sato/sdk/lsb because the other cases for these targets already cover the check point of "boot". Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-14qemuimagetest: Use the same image in sanity testing to fix the timeout issue ↵Jiajun Xu24
on autobuilder Fixes [BUGID #595] Because of the QEMU booting slowness issue(see bug #646 and #618), autobuilder may suffer a timeout issue when running sanity test. We introduce variable SHARE_IMAGE here to fix the issue. It is by default set to 1. Poky will copy latest built-out image and keep using it in sanity testing. If it is set to 0, latest built-out image will be copied and tested for each case, which will take much time. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-06qemuimagetest: Remove connman test for lsb image and fix one warning in ↵Jiajun Xu5
Test_Create_Qemu There is no connman in LSB image. So we need to remove connman test from it. And when we check if ip address fetched by Test_Fetch_Target_IP is valid, we should use "==" operator for string comparison. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-02qemuimagetest: Add basic function check for connmanJiajun Xu17
Add one case for connman sanity test. We check if connmand is running in background after booting and if there is always one connmand process running even connmand is executed by several times. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-02qemuimagetest: Add basic function check for gcc/g++/make command in targetJiajun Xu7
Add one case for compile tools sanity test in target, including gcc/g++/make. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-02qemuimagetest: Add basic function check for rpm commandJiajun Xu17
Add one case for rpm query sanity test. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2011-01-02qemuimagetest: Add basic function check for zypper commandJiajun Xu18
Add two cases for zypper sanity test. Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2010-12-07Add sanity test scenarios for -lsb imagesScott Garman5
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2010-11-14imagetest-qemu: Add sanity test cases for scp/shutdown in targetJiajun Xu16
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 Xu12
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-08-27test: Add scenario file for each target and support single case runningJiajun Xu12
Different test cases are needed for different targets. A folder "scenario" is created under scripts/qemuimage-tests to hold scenario files for different targets. Single case running is supported now. User can run single case together with a whole test suite by setting variable TEST_SCEN in local.conf. By default test cases in sanity suite will be ran. If you want to run other test suite or specific test case(e.g. bat or boot test case under sanity suite), list them like following. TEST_SCEN = "sanity bat sanity:boot" Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
2010-07-21Enable build dir outside of the poky directoryJoshua Lock2
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 Xu2
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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-01 05:06:34 +0000