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

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

2021-06-03T15:31:02+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/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

parselogs: Allow expected kernel messages for qemuppc64

2021-03-11T14:00:36+00:00

pseries machine emulation ends up with these three messages in kernel logs which are harmless, so ignore them for now https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5600561.html https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827162 (From OE-Core rev: f9a5dc7eeb99d211d728f8f7395aa22d4749e6a7) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

oeqa/weston: correctly run wayland-info when systemd is in use

2021-03-06T22:39:04+00:00

Under systemd weston's socket is in /run, not in /run/user/0. (From OE-Core rev: ea7dfd857ce3779745dccda0cbfd93b5e5de1a36) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

oeqa/pam: Need shadow installed for the tests

2021-02-27T22:40:41+00:00

Distros may not use shadow for login manager secondly login --help returns 1 only with shadow provided login utility, with busybox it returns normal 0, the testcase clearly assumes shadow being part of image, therefore add needed checks to ensure the pre-requisites are met (From OE-Core rev: 0820aeba74869bf6e85b200f39bc610a43ab9a7a) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

df.py: Add feature check for read-only-rootfs

2021-02-19T11:17:11+00:00

If the target is using a read-only rootfs, the available space on '/' will be zero. This will cause the test to incorrectly fail and skipping seems appropriate in this case. (From OE-Core rev: af1dbea3c9b9b42a3e6803b231e425423d70e210) Signed-off-by: Wes Lindauer Signed-off-by: Richard Purdie

oeqa/runlevel : add test for runlevels

2021-02-19T11:17:11+00:00

This test mimic the boot_from_runlevel_3 and boot_from_runlevel_5 test cases from oeqa/manual/bsp-hw.json. The boot_from_runlevel_3 and boot_from_runlevel_5 manual test cases should be remove from oeqa/manual/bsp-hw.json if this patch get merged. (From OE-Core rev: 6effd30f0e3726bc1f2eb7768c57c6b95eddb079) Signed-off-by: Teoh Jay Shen Signed-off-by: Richard Purdie

oeqa/usb_hid.py : add test to check the usb/human interface device status after suspend state

2021-02-03T21:45:49+00:00

This test mimic the Test_if_usb_hid_device_works_well_after_resume_from_suspend_state manual test case from oeqa/manual/bsp-hw.json. (From OE-Core rev: 23a3dc370a52907ee3261746405fb9b2af9e9a11) Signed-off-by: Teoh Jay Shen Signed-off-by: Richard Purdie