linux/poky.git/meta/lib/oeqa/runtime, branch daisy

lib/oeqa: add a test target controller for EFI targets

2014-03-31T21:53:46+00:00

The purpose of this module is to deploy a test image on a EFI-enabled hardware and run our runtime tests. A bit of background: - testimage.bbclass uses the concept of TEST_TARGET which is a class name that is responsible for target deploying. A layer can provide it's own TEST_TARGET. Right now has OE-core has a QemuTarget and a SimpleRemoteTarget (ssh into an already up and running machine and run tests), the default one being qemu. - basically testimage does something like: target.deploy() try: target.start() runTests() finally: target.stop() This module assumes a running EFI machine with gummiboot as bootloader and core-image-testmaster installed (or similar). Also your hardware under test has to be in a DHCP-enabled network that gives it the same IP for each reboot. One time setup (master image): - build core-image-testmaster with EFI_PROVIDER = "gummiboot" - install the image on the target Test image setup: - build your test image, e.g core-image-sato as you usually do, but with these in local.conf: IMAGE_FSTYPES += "tar.gz" - Now run the tests: INHERIT += "testimage" TEST_TARGET = "GummibootTarget" TEST_TARGET_IP = "192.168.2.3" bitbake core-image-sato -c testimage Other notes: - TEST_POWERCONTROL_CMD (togheter with TEST_POWERCONTROL_EXTRA_ARGS) can be a command that runs on the host and does power cycling. The test code passes one argument to that command: off, on or cycle (off then on). In my case I use something like TEST_POWERCONTROL_CMD="powercontrol.exp test 10.11.12.1 nuc1" in local.conf. Basically my expect script does: 'ssh test@10.11.12.1 "pyctl nuc1 " and runs a python script there that controls power for a label called nuc1'. The reason why my expect script has to ssh into another machine is because of network topology, and that machine is the one actually connected to the test rack and the power strip. That's why TEST_POWERCONTROL_CMD and _ARGS need to be customized for one's setup, the only requirement being that it accepts: on/off/cycle as the last argument. - if no command is defined it would use classic reboot. This is fine as long as the machine actually reboots (as in the ssh test hasn't failed), but it's useful for "simple-setup-with-one-board-on-the-desk" scenario, where some manual interaction is okay from time to time. [YOCTO #5614] (From OE-Core rev: e00f888a88d0851b088c232dec66418e575a2e90) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

oeqa/runtime/dmesg: Ignore DMA timeout errors

2014-03-02T17:25:28+00:00

We see these from qemu images on servers under load. They're not interesting and clutter the build output so lets ignore them. (From OE-Core rev: 053eba4885ab4016f7efc7899ec9e02df3384d11) Signed-off-by: Richard Purdie

oeqa/runtime: smart: don't run in auto mode when rpm is not the pm

2014-02-13T11:41:21+00:00

TEST_SUITES = "auto" would run smart tests even for non-rpm images, which is pointless. (From OE-Core rev: 1913f38d79a56f7d21999b6839835f967ca28abd) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

oeqa/utils: targetbuild: take proxy into account

2014-02-11T11:56:56+00:00

A previous commit broke downloads when proxies are involved, let's fix it. (From OE-Core rev: 97e263b99cbe8184a74f80738fd471cfdef29e0c) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

oeqa/runtime/systemd: remove race in settle()

2014-02-04T12:43:07+00:00

The settle() function had a race where services could still be activating at two minutes but then when the final log is output, they've activated. Remove this race and generally clean up the code. (From OE-Core rev: 8d107e0a828868702cfe035104c1f0b51da4291e) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa/runtime: syslog: update --help test

2014-02-02T11:22:12+00:00

busybox 1.22 now returns exitcode 0 instead of 1 for --help options, so this test needs to be updated when busybox gets upgraded to 1.22. https://bugs.busybox.net/show_bug.cgi?id=5612 http://git.busybox.net/busybox/commit/?id=efd0698f74caab0a0c8a51228b923ee142e8e278 (From OE-Core rev: 1e560d234b6d3040a7a9f0eb023f1e4a654be1ea) Signed-off-by: Stefan Stanacar Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

oeqa/runtime: smart: fix adding channels

2014-01-29T17:38:49+00:00

Without this it won't add core2-64 and similar channels, as the directory name in deploy_dir/rpm uses _ not - as the package arch. (From OE-Core rev: 14e3a8f58e309121760fec70619633281dd9d88c) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

oeqa/runtime: drop restartTarget method

2014-01-29T17:38:49+00:00

Restart is a property of a specific target, not of a test class, should a test really need to restart the target the direct method should be called. Also some tests used this to enforce more ram, which makes sense only for qemu targets only (and the inital reason this was needed isn't valid anymore, qemu machines had the default ram size bumped a while ago). (From OE-Core rev: 333a4326082e500bdbcd323af37e183e74adf617) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

oeqa/runtime: rpm: fix finding the test rpm file

2014-01-28T18:01:47+00:00

Translate TUNE_PKGARCH to find the right file (this used to work because tune for qemux86-64 used to be x86_64 now it's core2-64) Also, while using packagedata was nice, it's harder to make the test exportable and runnable outside of the build system. (where oe.packagedata isn't available) (From OE-Core rev: fd0e9ad4d295ca11b33c3e3e11069421dee834e8) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

oeqa/runtime/systemd: wait for services to start/fail

2014-01-14T11:33:50+00:00

When checking that no services have failed to start, actually wait for services to finish starting by waiting for there not be no units in the "activating" state. (From OE-Core rev: 4d6422a84eba005a6fd788ce18c9dd42b079e2a8) Signed-off-by: Ross Burton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie