linux/poky.git/meta/lib, branch 1.6_M1.rc1

lib/oeqa: targetcontrol.py: add abstraction for running tests on different targets

2013-12-03T17:45:52+00:00

Add a new module which abstracts the target object used by testimage.bbclass The purpose of this module is to move the deployment of a target from testimage.bbclass, basically abstracting different implementations of how we setup a target and how it runs commands. It allows to select one implementation or another by setting TEST_TARGET (currently to: "qemu" and "simpleremote"). QemuTarget is used to start a qemu instance (as it's currently done in testimage.bbclass) SimpleRemoteTarget is meant for a remote machine (by setting TEST_TARGET_IP) that's already up and running with network and ssh. Simply put, it opens the door for running the tests on different types of targets by adding new classes (maybe qemu-nfsroot or remote-special etc.). One could also override BaseTarget which currently uses the existing SSHControl module and add a serial implementation. [ YOCTO #5554 ] (From OE-Core rev: c1bfd4017f6f6502a68ceb3edf7d2027d02a309d) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

testimage: use the new targetcontrol.py module for running tests

2013-12-03T17:45:51+00:00

This patch makes the necessary changes for using the targetcontrol.py module so that one can run the same tests on a qemu instance or a remote machine based on the value of TEST_TARGET variable: "qemu" or "simpleremote". The default value is "qemu" which starts a qemu instance and it's the with what we currently have. With "simpleremote", the remote machine must be up with network and ssh and you need to set TEST_TARGET_IP with the IP address of the remote machine (it can still be a qemu instance that was manually started). Basically testimage.bbclass now does something along the lines of: - load tests -> deploy (prepare) / start target -> run tests. There were a couple of changes necessary for tests and also some cleanups/renames that were needed to adjust this change. (use ip everywhere when refering to target and server_ip when refering to host/build machine) Also two unnecessary and unsed methods were dropped from sshcontrol. [ YOCTO #5554 ] (From OE-Core rev: a7820350fa3271d78ed7476e02f4aef593be1125) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

lib/oeqa: use the new manifest file for determining if a package is installed

2013-12-03T17:45:51+00:00

Use the new manifest file instead of ${WORKDIR}/installed_pkgs.txt for determining if an image has a certain package, because installed_pkgs.txt goes away with rm_work enabled. We can't use the IMAGE_MANIFEST var for the file path because that relies on IMAGE_NAME which changes at every run (because of date), so we use the link which points to the last one built. [ YOCTO #5072 ] (From OE-Core rev: f57c83fc33583c140f668946f3f3e79b960aa9ee) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

lib/oeqa/selftest: add test modules for expected bitbake output and bitbake-layers

2013-12-03T17:45:51+00:00

Tests for bitbake-layers and expected output for some bitbake options. (From OE-Core rev: 8408a7700cd9cab4559ddae0bbe57f0d7fae5c37) Signed-off-by: Corneliu Stoicescu Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

lib/oeqa/selftest: buildoptions.py: add simple image build tests

2013-12-03T17:45:51+00:00

Build images and tests different build options like RM_OLD_IMAGE and for WARN_QA/ERROR_QA behaviour. (From OE-Core rev: 75d2a1a37a18a22b0da7ab5b30cf005c78bc313f) Signed-off-by: Alexandru Palalau Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

scripts/oe-selftest: script to run builds as unittest against bitbake or various scripts

2013-12-03T17:45:50+00:00

The purpose of oe-selftest is to run unittest modules added from meta/lib/oeqa/selftest, which are tests against bitbake tools. Right now the script it's useful for simple tests like: - "bitbake --someoption, change some metadata, bitbake X, check something" type scenarios (PR service, error output, etc) - or "bitbake-layers <...>" type scripts and yocto-bsp tools. This commit also adds some helper modules that the tests will use and a base class. Also, most of the tests will have a dependency on a meta-selftest layer which contains specially modified recipes/bbappends/include files for the purpose of the tests. The tests themselves will usually write to ".inc" files from the layer or in conf/selftest.inc (which is added as an include in local.conf at the start and removed at the end) It's a simple matter or sourcing the enviroment, adding the meta-selftest layer to bblayers.conf and running: oe-selftest to get some results. It would finish faster if at least a core-image-minimal was built before. [ YOCTO #4740 ] (From OE-Core rev: 41a4f8fb005328d3a631a9036ceb6dcf75754410) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

classes/buildhistory: add additional variables to image information

2013-12-03T17:45:50+00:00

Add PACKAGE_EXCLUDE and NO_RECOMMENDATIONS to the info we track for images, since these can change what ends up in the image. (From OE-Core rev: a10189366f180b87f5be20b66834b7e7a9bb8c12) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

sstatesig.py: Fix image regeneration issue

2013-11-29T10:49:25+00:00

With the "ABI safe" recipes, we've been excluding those from signatures. This is fine in the general case but in the specific case of image recipes it breaks. A good test case is the interfaces file. Editting this causes init-ifupdown to rebuild but not an image containing it (e.g. core-image-minimal). We need to ensure the checksums are added to the image recipes and this change does that. (From OE-Core rev: fd085f15e7cd093953f974f69277e130174d551d) Signed-off-by: Richard Purdie

oeqa/connman: disable unique test

2013-11-22T12:03:02+00:00

The connman unique test starts another instance of connmand and then does a ps to verify that there's only one of these running, on the assumption that the new one has quit because there's already one running (started by init). However, connmand is forking into the background straight away so there's a race between running ps and the second connmand discovering the first and exiting. This race can be seen because the test displays the output of ps, and by the time that second ps has been executed the new connmand has exited. This is a classic race condition and on a heavily loaded autobuilder inserting an arbitrary sleep isn't wise. In the scheme of things this test isn't very useful, so delete it. (From OE-Core rev: 80ef721140c79e29430d0a5692a5c176db0061e6) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

buildhistory_analysis: fix error when comparing image contents

2013-11-18T12:44:04+00:00

OE-Core commit b7de1eaac9eed559b2d68058f5de67de74a6cb58 added an extra argument to the compare_dict_blobs() function but missed adding the argument to one call to compare two versions of the image-info.txt file. (From OE-Core rev: 24a45d752c3e3d0d8b59c040355e4fe7de22b041) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie