]> code.ossystems Code Review - openembedded-core.git/commit
oeqa/runqemu: Support RUNQEMU_TMPFS_DIR as a location to copy snapshot images to
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 31 Mar 2021 21:41:52 +0000 (22:41 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 6 Apr 2021 08:30:05 +0000 (09:30 +0100)
commitfd1c26ab426c3699ffd8082b83d65a84c8eb8bff
tree82637904efc72c583b179935710f794dfe38b954
parent275738c3f2116de9b812b46e00d80b4de6975d7f
oeqa/runqemu: Support RUNQEMU_TMPFS_DIR as a location to copy snapshot images to

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.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/testimage.bbclass
meta/lib/oeqa/core/target/qemu.py
meta/lib/oeqa/targetcontrol.py
meta/lib/oeqa/utils/qemurunner.py
meta/lib/oeqa/utils/qemutinyrunner.py
scripts/runqemu