From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
qemu-ppc@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>
Subject: [PATCH 0/4] tests/avocado: Fixes for ppc_hv_tests.py
Date: Thu, 28 Mar 2024 14:15:23 +1000 [thread overview]
Message-ID: <20240328041527.2602823-1-npiggin@gmail.com> (raw)
This series is a bunch of fixes for ppc_hv_tests.py. It includes a
generic avocado patch that I've posted before, but that seems to
only really affect ppc_hv_tests.py (I haven't seen other tests wait
for console after executing a command like this).
If people feel patch 3 is too late for 9.0, then patch 4 should be
left of too, but 1 and 2 at least should resolve some CI failures
and are self-contained.
Thanks,
Nick
Nicholas Piggin (4):
tests/avocado: Fix ppc_hv_tests.py xorriso dependency guard
tests/avocado: ppc_hv_tests.py set alpine time before setup-alpine
tests/avocado: exec_command should not consume console output
tests/avocado: Mark ppc_hv_tests.py as non-flaky after fixed console
interaction
tests/avocado/avocado_qemu/__init__.py | 7 +++++++
tests/avocado/ppc_hv_tests.py | 7 +++++--
2 files changed, 12 insertions(+), 2 deletions(-)
--
2.42.0
next reply other threads:[~2024-03-28 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 4:15 Nicholas Piggin [this message]
2024-03-28 4:15 ` [PATCH 1/4] tests/avocado: Fix ppc_hv_tests.py xorriso dependency guard Nicholas Piggin
2024-03-28 4:15 ` [PATCH 2/4] tests/avocado: ppc_hv_tests.py set alpine time before setup-alpine Nicholas Piggin
2024-03-28 4:15 ` [PATCH 3/4] tests/avocado: exec_command should not consume console output Nicholas Piggin
2024-03-28 4:15 ` [PATCH 4/4] tests/avocado: Mark ppc_hv_tests.py as non-flaky after fixed console interaction Nicholas Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240328041527.2602823-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).