From: Nicholas Piggin Date: Wed, 24 Jan 2024 05:49:10 +0000 (+1000) Subject: tests/avocado: improve flaky ppc/pnv boot_linux_console.py test X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=458a6aa3b3346c33a9be9441f2f17f2937e88b72;p=qemu.git tests/avocado: improve flaky ppc/pnv boot_linux_console.py test The expected MTD partition detection output does not always appear on the console, despite the test reaching the boot loader and the string appearing in dmesg. Possibly due to an init script that quietens the console output. Using an earlier log message improves reliability. Reviewed-by: Cédric Le Goater Signed-off-by: Nicholas Piggin --- diff --git a/tests/avocado/boot_linux_console.py b/tests/avocado/boot_linux_console.py index 3f0180e1f8..af104fff1c 100644 --- a/tests/avocado/boot_linux_console.py +++ b/tests/avocado/boot_linux_console.py @@ -1368,7 +1368,8 @@ class BootLinuxConsole(LinuxKernelTest): self.wait_for_console_pattern("CPU: " + proc + " generation processor") self.wait_for_console_pattern("zImage starting: loaded") self.wait_for_console_pattern("Run /init as init process") - self.wait_for_console_pattern("Creating 1 MTD partitions") + # Device detection output driven by udev probing is sometimes cut off + # from console output, suspect S14silence-console init script. def test_ppc_powernv8(self): """