linux/poky.git/meta/lib, branch yocto-3.1.1

qemurunner: fix ip fallback detection

2020-06-05T20:36:30+00:00

When falling back from detecting ip from /proc/./cmdline the output of runqemu is acutally 'Network configuration: ip=192.168.7.2::192.168.7.1::255.255.255.0' which doesn't match the given regex and leading to run failure, although IP is detectable. Fix regex by inserting an optional 'ip=' prefix to first IP (From OE-Core rev: 9c2efe41d5d894094552c4bbc4180675a5aac751) Signed-off-by: Konrad Weihmann Signed-off-by: Richard Purdie (cherry picked from commit 75f2471d15fab024775c59cb70c54e3f25f9ae72) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

terminal.py: do not stop searching for auto

2020-06-05T20:36:30+00:00

If a terminal fails to spawn() we should continue looking. gnome-terminal, in particular can be present but not start. (From OE-Core rev: 5ca00faa9c085fef1781b66561de461e9cc5b117) Signed-off-by: Joe Slater Signed-off-by: Richard Purdie (cherry picked from commit 6e4babdeee38d32002a4c9129e77466ae4156dd7) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oeqa/concurrencytest: don't delete build directory for failed tests

2020-06-05T20:36:30+00:00

(From OE-Core rev: be24033acee75526a3a66c12606ef67dcb52a7ee) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie (cherry picked from commit 3d5aa170d2e88b852bd2a4452aab9311a24badef) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

testresults.json: add duration of the tests as well

2020-05-28T17:15:29+00:00

This is printed by testimage, but isn't actually saved. It's a useful metric for tracking execution times. (From OE-Core rev: 866c652c850d9e23300218fcbe0b9e4b3ade2ebf) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie (cherry picked from commit 8fc19639f47b959a141dae231395bbababa644e1) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

selftest/imagefeatures: Enable sanity test for IMAGE_GEN_DEBUGFS

2020-05-22T15:23:24+00:00

Add new testcase to check IMAGE_GEN_DEBUGFS. Test makes sure that debug filesystem is created accordingly. Test also check for debug symbols for some packages as suggested by Ross Burton. [YOCTO #10906] (From OE-Core rev: 1038195fe9823c93cf20e2d256865171e0c915c4) Signed-off-by: Humberto Ibarra Signed-off-by: Yeoh Ee Peng Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oeqa/qemurunner: Clean up failure handling

2020-05-07T12:03:30+00:00

If you fail to setup the tap devices, runqemu will error quickly however stdout/stderr are not shown to the user, instead a SystemExit traceback is shown. This could explain some long since unexplained failures on the autobuilder. Rework the error handling so SystemExit isn't used and the standard log failure messages can be shown. The code could likely ultimatley need some restructuring to work effectively. (From OE-Core rev: 83b8e66b66aa9848ed9c8761a21cb47c6443d0c6) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

targetcontrol: Fix leaking log handler

2020-05-07T12:03:30+00:00

We had a mystery failure on the autobuilder where runqemu appeared to be failing as a logfile directory no longer existed. The key to reproducing was running a runqemu where the image was deleted (as devtool does), then running another runqemu test. E.g.: 'oe-selftest -r devtool.DevtoolExtractTests.test_devtool_deploy_target wic.Wic2.test_qemu_efi' This then tries to write to the logfile from the first test, the image directory was deleted and we get strange failures. The fix is to remove the logging handler when qemu is stopped. (From OE-Core rev: 924b020eacf111b4fd4d731b363084e254a3422d) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oeqa/selftest: Add test for conflicting sysroot provider

2020-05-07T12:03:30+00:00

sysroot-test depends on virtual/sysroot-test which we build for one machine, switch machine, switch provider of virtual/sysroot-test and check that the sysroot is correctly cleaned up. The files in the two providers overlap so can cause errors if the sysroot code doesn't function correctly. Yes, sysroot-test should be machine specific really to avoid this, however the sysroot cleanup should also work. This adds a test for bug: [YOCTO #13702] (From OE-Core rev: 31a8b4935e673aba8a1147c4a2fb510b1a8bc3ce) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

parselogs.py: ignore pulseaudio startup warning messages

2020-05-05T07:45:31+00:00

If set default syslog to rsyslog, we can see below messages in user.log, [pulseaudio] authkey.c: Failed to open cookie file [pulseaudio] authkey.c: Failed to load authentication key They are only warnings when cookie file is not found. And PulseAudio will create it if it doesn't exist. refer: https://wiki.archlinux.org/index.php/PulseAudio/Configuration https://lists.freedesktop.org/archives/pulseaudio-discuss/2014-December/022719.html (From OE-Core rev: 2cc3fac9cd1a0d77931c9e49dbe2941fa8619c51) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

parselogs.py: update network interface related messages

2020-04-07T20:57:16+00:00

along with systemd upgrade, error message related change network interface have changed, update it. (From OE-Core rev: a8b2cd7470bcc25527577b95a26a0a528949232d) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie