linux/poky.git/meta/classes/testimage.bbclass, branch 3.5_M1

go-helloworld: test at runtime

2021-11-29T23:07:13+00:00

This adds a smoke check for whether the Go toolchain actually produces working executables across a range of architectures. (From OE-Core rev: 2819bb2cf22c6cfcaeaee79f0280097ec9cb9327) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

testimage.bbclass: request the use of kvm by default

2021-11-29T23:07:13+00:00

In almost all cases there is no need to explicitly ask for it via local.conf or similar custom config: it is enabled in qemu_use_kvm() if target_arch == build_arch or both of them are x86 archs, and QEMU_USE_KVM is set. If that heuristic doesn't work, QEMU_USE_KVM = "" will do the disabling. (From OE-Core rev: c2a2d475a976225e3a4eb687af6d2a62dca1d2bf) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

testimage: remove target_modules_path

2021-10-23T16:42:28+00:00

There is no need to pass target_modules_path anymore, so remove it. (From OE-Core rev: 3d579fb7e4eb96fe0e20e2a7a5948940ca086f99) Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

testimage: fix unclosed testdata file

2021-10-17T10:56:32+00:00

(From OE-Core rev: 0c192a97e3e1c015a48667d6903cc07a8b2620e4) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

testimage: remove aarch64 xorg exclusion

2021-09-21T22:44:08+00:00

aarch64/qemuarm64 has had graphics support for some time. Remove this exclusion and allow graphics tests to be against qemuarm64. (From OE-Core rev: 1b436e4894663fa76865636b0b41c0c1503cc3bf) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie

testimage: symlink the task log and qemu console log to tmp/log/oeqa

2021-09-21T22:44:08+00:00

This makes it easier for the AB scripts (particularly, collect-results) to access and archive these items, as they can contain useful information when ptests or other qemu tests fail (and also if they don't fail). [YOCTO #14518] (From OE-Core rev: 1965b344abcff0ba584136f929b4a14645f1585e) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

Convert to new override syntax

2021-08-02T14:44:10+00:00

This is the result of automated script conversion: scripts/contrib/convert-overrides.py converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie

testimage.bbclass: Add dump-guest-memory cmd

2021-07-02T22:14:33+00:00

This command takes a set of command arguments, one of which requires a filename so use %s which the MonitorDumper will translate to a unique filename in the dated qmp directory. CMD Before: {paging:false,protocol:file:%s.img} CMD After: {paging:false,protocol:file:/yocto/poky/build/tmp/log/runtime-hostdump/qmp_00_dump-guest-memory.img} (From OE-Core rev: 563e78491be3763f53f9ea53241853b099f5747b) Signed-off-by: Saul Wold Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

qemurunner: Add support for qmp commands

2021-04-27T14:11:47+00:00

This adds support for the Qemu Machine Protocol [0] extending the current dump process for Host and Target. The commands are added in the testimage.bbclass. Currently, we setup qemu to stall until qmp gets connected and sends the initialization and continue commands, this works correctly. If the UNIX Socket does not exist, we wait an timeout to ensure to socket file is created. With this version, the monitor_dumper is created in OEQemuTarget but then set in OESSHTarget as that's where we get the SSH failure happens. Python's @property is used to create a setter/getter type of setup in OESSHTarget to get overridden by OEQemuTarget. By default the data is currently dumped to files for each command in TMPDIR/log/runtime-hostdump/_qmp/unknown__qemu_monitor as this is the naming convenstion in the dump.py code. We use the qmp.py from qemu, which needs to get installed in the recipe-sysroot-native of the target image. [0] https://github.com/qemu/qemu/blob/master/docs/interop/qmp-spec.txt (From OE-Core rev: 42af4cd2df72fc8ed9deb3fde4312909842fcf91) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

oeqa/runqemu: Support RUNQEMU_TMPFS_DIR as a location to copy snapshot images to

2021-04-06T08:30:10+00:00

We have a working theory that IO queues on the autobuilder are impacting runtime testing under qemu, particularly async writes which inice does not influence. We already pass the snapshot option to qemu which copies the image and runs out of the copy. Add in the ability to copy the image to a specificed location which can be a tmpfs. This means that writes to the image would no longer be blocked by other writes to disk in the system. Preliminary tests show that this does improve the qemu errors at the expense of sometimes showing qemu startup timeouts as on a loaded system with a large test image, it can take longer than 120s to copy the image to tmpfs. Having a most consistent failure mode for loaded tests is probably desireable though. (From OE-Core rev: fd1c26ab426c3699ffd8082b83d65a84c8eb8bff) Signed-off-by: Richard Purdie