This test seems to be flaky, it hangs without ever getting the
MTD partition message. But I think it might be the init process
quieting the kernel console messages that just happens to run
first. P10 seems to just hit this up more, maybe small timing
differences.
So I'll send a patch to adjust the tets harness to avoid it.
Thanks,
Nick
On Thu Jan 18, 2024 at 12:12 AM AEST, Nicholas Piggin wrote:
> Add test for POWER10.
>
> Reviewed-by: Cédric Le Goater <c...@kaod.org>
> Signed-off-by: Nicholas Piggin <npig...@gmail.com>
> ---
> tests/avocado/boot_linux_console.py | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/tests/avocado/boot_linux_console.py
> b/tests/avocado/boot_linux_console.py
> index 3f0180e1f8..4f05bb7441 100644
> --- a/tests/avocado/boot_linux_console.py
> +++ b/tests/avocado/boot_linux_console.py
> @@ -1386,6 +1386,14 @@ def test_ppc_powernv9(self):
> """
> self.do_test_ppc64_powernv('P9')
>
> + def test_ppc_powernv10(self):
> + """
> + :avocado: tags=arch:ppc64
> + :avocado: tags=machine:powernv10
> + :avocado: tags=accel:tcg
> + """
> + self.do_test_ppc64_powernv('P10')
> +
> def test_ppc_g3beige(self):
> """
> :avocado: tags=arch:ppc
