summaryrefslogtreecommitdiff
path: root/scripts/qemuimage-tests/sanity/connman
Commit message (Collapse)AuthorAgeFilesLines
* Replace POKYBASE with COREBASERichard Purdie2011-04-201-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename poky-qemu to runqemuRichard Purdie2011-04-201-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimagetest: Use same image during sanity testing instead of copying a new ↵Jiajun Xu2011-01-201-1/+1
| | | | | | | | | | | | | | | | | 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>
* qemuimagetest: Use the same image in sanity testing to fix the timeout issue ↵Jiajun Xu2011-01-141-1/+1
| | | | | | | | | | | | | | | 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>
* qemuimagetest: Add basic function check for connmanJiajun Xu2011-01-021-0/+52
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>