linux/poky.git/meta/lib/oeqa/runtime, branch yocto-3.3.5

oeqa/parselogs: Fix quoting

2021-12-15T07:40:29+00:00

Fix deprecation warnings about invalid escape sequences. (From OE-Core rev: 85024cac98791fa39b73de7f3512a690277ffc7c) Signed-off-by: Richard Purdie (cherry picked from commit 43542614395150e8fa34133ba0fc7ee90f215bcb) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oeqa/runtime/parselogs: Make DVD ata error apply to all qemux86 machines

2021-09-09T09:19:42+00:00

This log checking fix is needed for both qemux86 and qemux86-64 so move to the common section. [YOCTO #14528] (From OE-Core rev: f749f4e73e7c5c5f42dc91672d2c7df0ad7b3734) Signed-off-by: Richard Purdie (cherry picked from commit 2475ce68f0bc1f342c75364dfcfaf7f30499badf) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

parselogs.py: ignore intermittent CD/DVDROM identification failure

2021-09-09T09:19:42+00:00

We don't use the CD/DVD ROM drive in any of our tests, but it periodically fails discovery and that leads to a QA error: [ 6.403477] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) The only way to disable the optical ROM drive in qemu is to use the '-nodefaults' option, which disables the CDROM (among other things). We can't be sure that none of our tests, or extended users are relying on default devices, so using that option is more of a risk than adding the message to our ignore list. To date, no one has sent a patch to just disable the optical drive (either in qemu or the BIOS), but that is something we could consider in the future. [YOCTO #14528] (From OE-Core rev: fc5c448d94e63bebb97de83113697c5cefe27116) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie (cherry picked from commit 143fc5504539c69752ca87717507c197a8920ce5) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oeqa/runtime/cases: make date.DateTest.test_date more reliable

2021-08-26T07:32:13+00:00

The test uses the broken out time and can only handle about 59s of delay, use a UNIX timestamp to allow for up to a 300s delay. [YOCTO #14463] (From OE-Core rev: 09e238635c8d4cd595c2233a14c2ce1cbb9e5162) Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit b705e9373acd4119da75af4eb96ec92cc964aa86) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oeqa/runtime/cases/ptest: Increase test timeout from 300s to 450s

2021-08-14T11:01:44+00:00

Some tests such as lttng-tools are marginal and timing out on the autobuilder with the current 300s default. Increase to avoid this noise in the ptest failures list. (From OE-Core rev: 616f0981c8a4ecd358c70c63f88b0bea51cf4e77) Signed-off-by: Richard Purdie (cherry picked from commit 5fb902a52e35130af6b0735a087c709daa35655f) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

parselogs.py: qemuarm should be qemuarmv5

2021-08-14T11:01:43+00:00

All of the errors being masked off for qemuarm are legacy from before the migration of qemuarm to qemuarmv5. Rename the machine to that to allow for qemuarmv5 to pass parselog test. Light testing shows no errors in dmesg for qemuarm. (From OE-Core rev: 5dc6645397fa8072428a17ea904d8e0b110dc12c) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie (cherry picked from commit 701a58504de15b244b970908f2de0971a35b5a09) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

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