summaryrefslogtreecommitdiffstats
path: root/meta/lib/oeqa/runtime/systemd.py
diff options
context:
space:
mode:
authorStefan Stanacar <stefanx.stanacar@intel.com>2014-03-30 17:47:34 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-31 22:53:46 +0100
commit2764a40093644595cad9c095fb344912f9dc60fa (patch)
tree2b1ad6e82dca4281bacd2093b990b728716bbf19 /meta/lib/oeqa/runtime/systemd.py
parenta4447e365026b6f1af74b48a4fbd5059c05afdbd (diff)
downloadpoky-2764a40093644595cad9c095fb344912f9dc60fa.tar.gz
recipes-extended: add master image for testing purposes
Add a custom recipe with custom initramfs and installers, that makes it easy to deploy a master image for testing purposes. We need a master image running on the target hardware, that should be a known good build, with a set of utilities installed so that we use it to deploy the images under test. This core-image-testmaster recipe isn't a requirement per se, any image can be used as long as the required conditions are met. The test code assumes: - that the device has a second rootfs labeled as testrootfs - it has a properly configured bootloader entry (called test) for the second kernel and rootfs - the master image has a /etc/masterimage file so it can differentiate between master and test images - the master image has tar, mount, bash (basically the normal linux utilities not the busybox ones) [YOCTO #5614] (From OE-Core rev: dea237ccd9407288cd3a73e1deca270619dd6d4a) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/oeqa/runtime/systemd.py')
0 files changed, 0 insertions, 0 deletions