From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Kautuk Consul" <kconsul@linux.vnet.ibm.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v4 1/2] avocado_qemu/__init__.py: factor out the qemu-img finding
Date: Fri, 21 Apr 2023 08:03:25 +0200 [thread overview]
Message-ID: <826f3ebc-ec1a-1a05-183b-3edd0291826c@linaro.org> (raw)
In-Reply-To: <20230421042322.684093-2-kconsul@linux.vnet.ibm.com>
On 21/4/23 06:23, Kautuk Consul wrote:
> Factor out the code that finds the qemu-img binary in the
> QemuSystemTest class and create a new get_qemu_img() function
> with it. This function will get called also from the new code
> in tuxrun_baselines.py avocado test-case.
>
> Signed-off-by: Kautuk Consul <kconsul@linux.vnet.ibm.com>
> ---
> tests/avocado/avocado_qemu/__init__.py | 27 +++++++++++++++-----------
> 1 file changed, 16 insertions(+), 11 deletions(-)
Suggested-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-04-21 6:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 4:23 [PATCH v4 0/2] Improve code coverage for ppc64 Kautuk Consul
2023-04-21 4:23 ` [PATCH v4 1/2] avocado_qemu/__init__.py: factor out the qemu-img finding Kautuk Consul
2023-04-21 6:03 ` Philippe Mathieu-Daudé [this message]
2023-04-21 6:37 ` Kautuk Consul
2023-04-21 6:55 ` Harsh Prateek Bora
2023-04-21 4:23 ` [PATCH v4 2/2] tests/avocado/tuxrun_baselines.py: improve code coverage for ppc64 Kautuk Consul
2023-04-21 6:02 ` Philippe Mathieu-Daudé
2023-04-21 6:38 ` Kautuk Consul
2023-04-21 6:40 ` Harsh Prateek Bora
2023-04-21 6:36 ` [PATCH v4 0/2] Improve " Kautuk Consul
2023-04-21 13:29 ` Alex Bennée
2023-04-24 4:20 ` Kautuk Consul
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=826f3ebc-ec1a-1a05-183b-3edd0291826c@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=kconsul@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--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).