mirror of
https://git.yoctoproject.org/poky
synced 2026-02-10 10:43:02 +01:00
f484b4e183
Discussion with the libinput maintainer has confirmed that many of the libinput test cases need to run on a relatively unloaded system, because input handling is by definition time-sensitive and any event mismatches are considered a failure to avoid broken code hiding. We can't expect libinput to run on an otherside unloaded machine because the autobuilder ptests execute in a qemu at the same time as builds can be happening. We can however reduce the amount of parallellism happening in the libinput test suite to give it a better chance of succeeding. This may not be enough, but it's worth a go. [ YOCTO #14164 ] (From OE-Core rev: bd33e62fba70e8461d0efbee04841db9a0c1ff9d) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 5702f7c489ed45b7f4a69c78aa8215e2c98e21c4) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
QEMU Emulation Targets ====================== To simplify development, the build system supports building images to work with the QEMU emulator in system emulation mode. Several architectures are currently supported in 32 and 64 bit variants: * ARM (qemuarm + qemuarm64) * x86 (qemux86 + qemux86-64) * PowerPC (qemuppc only) * MIPS (qemumips + qemumips64) Use of the QEMU images is covered in the Yocto Project Reference Manual. The appropriate MACHINE variable value corresponding to the target is given in brackets.