From: "Alex Bennée" <alex.bennee@linaro.org>
To: Kautuk Consul <kconsul@linux.vnet.ibm.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v4 0/2] Improve code coverage for ppc64
Date: Fri, 21 Apr 2023 14:29:38 +0100 [thread overview]
Message-ID: <875y9pbbrk.fsf@linaro.org> (raw)
In-Reply-To: <20230421042322.684093-1-kconsul@linux.vnet.ibm.com>
Kautuk Consul <kconsul@linux.vnet.ibm.com> writes:
> Commit c0c8687ef0fd990db8db1655a8a6c5a5e35dd4bb disabled the
> boot_linux.py test-case due to which the code coverage for ppc
> decreased by around 2%. As per the discussion on
> https://lore.kernel.org/qemu-devel/87sfdpqcy4.fsf@linaro.org/ it
> was mentioned that the baseline test for ppc64 could be modified
> to make up this 2% code coverage. This patchset attempts to achieve
> this 2% code coverage by adding various device command line
> arguments (to ./qemu-system-ppc64) in the tuxrun_baselines.py
> test-case.
I've pulled the first patch into my testing/next, but the second
conflicts with the inflight patch which adds checksums:
Message-Id: <20230417134321.3627231-3-alex.bennee@linaro.org>
Date: Mon, 17 Apr 2023 14:43:17 +0100
Subject: [PATCH v4 2/6] tests/avocado: use the new snapshots for testing
From: =?UTF-8?q?Alex=20Benn=C3=A9e?= <alex.bennee@linaro.org>
You can either wait and re-base once the PR goes in (I'll send a pre-PR
Monday) or do you can re-base directly off my branch at:
https://gitlab.com/stsquad/qemu/-/tree/testing/next
and send the tested patch mentioning its based off my testing/next and
I'll include it in the pre-PR.
>
> Changes since v3:
> - Create a common ppc64_common_tuxrun routine in tuxrun_baselines.py
> and call that from the ppc64 and ppc64le test case routines.
>
> Kautuk Consul (2):
> avocado_qemu/__init__.py: factor out the qemu-img finding
> tests/avocado/tuxrun_baselines.py: improve code coverage for ppc64
>
> tests/avocado/avocado_qemu/__init__.py | 27 +++++-----
> tests/avocado/tuxrun_baselines.py | 68 ++++++++++++++++++++++++--
> 2 files changed, 80 insertions(+), 15 deletions(-)
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-04-21 13:34 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é
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 [this message]
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=875y9pbbrk.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=kconsul@linux.vnet.ibm.com \
--cc=philmd@linaro.org \
--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).