From: Kautuk Consul <kconsul@linux.vnet.ibm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	"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>
Cc: qemu-devel@nongnu.org, Kautuk Consul <kconsul@linux.vnet.ibm.com>
Subject: [PATCH v4 0/2] Improve code coverage for ppc64
Date: Thu, 20 Apr 2023 23:23:20 -0500	[thread overview]
Message-ID: <20230421042322.684093-1-kconsul@linux.vnet.ibm.com> (raw)
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.
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(-)
-- 
2.25.1
next             reply	other threads:[~2023-04-21  4:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21  4:23 Kautuk Consul [this message]
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
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=20230421042322.684093-1-kconsul@linux.vnet.ibm.com \
    --to=kconsul@linux.vnet.ibm.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.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).