linux/poky.git/meta/lib/oeqa, branch hardknott-next

oeqa/runtime/rpm: Drop log message counting test component

2021-06-02T22:32:45+00:00

This test is flawed since multiple parts of the system can write to the log and we obtain different numbers of log messages depending on factors we can't control. Drop the log testing component of the test. [YOCTO #12465] (From OE-Core rev: 6ca1047e98a1c8bc305a3f40ad1919c5038e1698) Signed-off-by: Richard Purdie

oeqa/qemurunner: Improve handling of run_serial for shutdown commands

2021-05-15T16:18:21+00:00

When running a shutdown command, the serial port can close without the command returning. This is seen as the socket being readable but having no data. Change the way this case is handled in the code to avoid tracebacks. (From OE-Core rev: a72572532b976a4c3e8fa68fe63f63e39399ee88) Signed-off-by: Richard Purdie (cherry picked from commit 396a3ba884820d040c91f7592daf20ac28c49b5d) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oeqa/qemurunner: Fix binary vs str issue

2021-05-15T16:18:21+00:00

The recent logging changes for qemurunner showed up as errors on the autobuilder where decode couldn't be called on the returned string. Since the code returns binary data, return b'' instead of '' to match to avoid tracebacks. One of these cases was newly added, copied from the other which has been there for a long time, always broken. (From OE-Core rev: 000feb98ff99e74d6118fc3f53330b8e975923d9) Signed-off-by: Richard Purdie (cherry picked from commit b8995b27db265b0a0b2d2ca595915f70f9f96e07) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oeqa/qemurunner: Improve logging thread exit handling for qemu shutdown test

2021-05-15T16:18:21+00:00

Rather than totally disabling the logging, inform it we're about to exit so we can log messages over the exit cleanly too. This aids debugging. It also avoids a race where the logging handler could still error whilst shutting down. Also remove a race window by notificing the handler of the shutdown first, before triggering it. This removes a race window I watched in local testing. (From OE-Core rev: 7f931dce4484a2740b419b2d25830fc453748a0c) Signed-off-by: Richard Purdie (cherry picked from commit 0e19f31a1005f94105e1cef252abfffcef2aafad) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

Revert "oeqa: Set LD_LIBRARY_PATH when executing native commands"

2021-05-11T11:02:29+00:00

LD_LIBRARY_PATH leaks into host executables too, and breaks them as they are not uninative-enabled. E.g. on ubuntu 18.04 trying to run host bash with a sysroot that was built on Fedora 33: akanavin@ubuntu1804-ty-3:/home/pokybuild/yocto-worker/oe-selftest-ubuntu/build/build-st-24341/tmp/work/x86_64-linux/gnupg-native/2.3.1-r0/recipe-sysroot-native$ LD_LIBRARY_PATH=./usr/lib /bin/bash /bin/bash: ./usr/lib/libtinfo.so.5: no version information available (required by /bin/bash) /bin/bash: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./usr/lib/libtinfo.so.5) This was seen e.g. here: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/2090/steps/14/logs/stdio (From OE-Core rev: efcc95f25843ed5aa825ebc55985eaf4660a498a) Signed-off-by: Richard Purdie (cherry picked from commit 0e9850486b74a3de934527ca1077df001d3a8d22) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

meta/lib/oeqa/core/tests/cases/timeout.py: add a testcase for the previous fix

2021-05-04T21:57:51+00:00

This is the sequence that didn't properly operate: - a test case that skips and isn't executed - a second test case that is skipped via a dependency decorator, and sets a timeout - a third test case that takes longer than the timeout from the second test case Without the fix, the timeout is not cleared, and the third test case is erroneously aborted. With the fix, the timeout is cleared and the third test case is able to complete. (From OE-Core rev: 4665008247cd4bd28da8c8b56c8c604e2e24d2cb) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie (cherry picked from commit 54ef07a9aa1af8f41cfb9a4802929c918efc43c8) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oeqa: tear down oeqa decorators if one of them raises an exception in setup

2021-05-04T21:57:51+00:00

Some of the decorators need proper cleanup, such as OETimeout which sets a signal handler that needs to be cleared via teardown. If this is not done then the signal gets called later with unpredictable effects. This can be seen if there's a test that is skipped via a decorator and sets a timeout at the same time: the timeout isn't cleared, and is invoked later in a completely unrelated context. The test case for this is added in the next commit. (From OE-Core rev: be45a8271c06ffbb5d97afd33bb15b1143b6cf8d) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie (cherry picked from commit f42a08e1aabf1ca57e0c09d69fb69cc717c7f156) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oeqa/runtime: space needed

2021-04-30T13:37:25+00:00

Messages are currently being printed as: Test requires dropbear, oropenssh-sshd to be installed but should be Test requires dropbear, or openssh-sshd to be installed Adding the space after the 'or' corrects this. (From OE-Core rev: f85c993bc4535dc42b89e87050d43c018c100f58) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie (cherry picked from commit 51596e0f8cebe1607ab64ffb018d51e815c0ee4b) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

parselogs: ignore floppy error on qemu-system-x86 at boot stage

2021-04-30T13:37:25+00:00

We can disable floppy drive by BIOS on a hardware, but an empty floppy drive is connected by default on qemu-system-x86. Linux usually detect the device and modprode the matched floppy.ko at the boot stage. Due to we don't specify a floppy deivce in qemu boot arguments, then the errors about floppy reading comes out. It is harmless and normal, so we could ignore this error message on qemux86. Seen if kernel-modules is included in the image which pulls in the relavent kernel module. https://lists.gnu.org/archive/html/qemu-devel/2021-04/msg01402.html (From OE-Core rev: 0e449143839f8de338b4a18fb27e8380d80e9b2f) Signed-off-by: Yanfei Xu Signed-off-by: Richard Purdie (cherry picked from commit 3359f23ee9351c70997d5e0a17d17d1e47d59623) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oeqa/runtime/cases: Only disable/enable for current boot

2021-04-30T13:37:25+00:00

Previously doing a stop/start worked, but using a disable/enable does not work on a read-only rootfs. Add a --runtime flag to systemctl so that systemd only modifies the current boot and does not attempt to write to the filesystem. This also keeps the test from making a permanent (one could argue policy) change to the running system being tested. i.e. What if the image being tested had intentionally disabled the timesyncd service in preference to using chrony or ntpd? The test shouldn't assume that the user wants the timesyncd service enabled. (From OE-Core rev: 49a6632aa789fca8085a91b5b7c749aef3db4e0e) Signed-off-by: Wes Lindauer Signed-off-by: Richard Purdie (cherry picked from commit 43dd83b6a325589368c980a3f17cab90935aaeb0) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie