diff options
author | Jiajun Xu <jiajun.xu@intel.com> | 2011-01-19 00:22:30 +0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-01-20 21:36:57 +0000 |
commit | 3e052919c9307ba73a1db0f705b7dc1a677cb80f (patch) | |
tree | 14861629035fb78eaae19645801f49a608536ecf /meta/recipes-devtools/python/python-pygobject | |
parent | 50b208612945c638e3f4965ebf90ade4aac5b636 (diff) | |
download | openembedded-core-3e052919c9307ba73a1db0f705b7dc1a677cb80f.tar.gz openembedded-core-3e052919c9307ba73a1db0f705b7dc1a677cb80f.tar.bz2 openembedded-core-3e052919c9307ba73a1db0f705b7dc1a677cb80f.tar.xz openembedded-core-3e052919c9307ba73a1db0f705b7dc1a677cb80f.zip |
qemuimagetest: Use same image during sanity testing instead of copying a new 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>
Diffstat (limited to 'meta/recipes-devtools/python/python-pygobject')
0 files changed, 0 insertions, 0 deletions