From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: qemu-devel@nongnu.org
Cc: wrampazz@redhat.com, philmd@redhat.com, pavel.dovgaluk@ispras.ru,
crosa@redhat.com, pbonzini@redhat.com, alex.bennee@linaro.org,
aurelien@aurel32.net
Subject: [PATCH 0/3] tests/acceptance: Handle tests with "cpu" tag
Date: Wed, 24 Feb 2021 18:26:51 -0300 [thread overview]
Message-ID: <20210224212654.1146167-1-wainersm@redhat.com> (raw)
Currently the acceptance tests tagged with "machine" have the "-M TYPE"
automatically added to the list of arguments of the QEMUMachine object.
In other words, that option is passed to the launched QEMU. On this
series it is implemented the same feature but instead for tests marked
with "cpu".
There is a caveat, however, in case the test needs additional arguments to
the CPU type they cannot be passed via tag, because the tags parser split
values by comma. For example, in tests/acceptance/x86_cpu_model_versions.py,
there are cases where:
* -cpu is set to "Cascadelake-Server,x-force-features=on,check=off,enforce=off"
* if it was tagged like "cpu:Cascadelake-Server,x-force-features=on,check=off,enforce=off"
then the parser would break it into 4 tags ("cpu:Cascadelake-Server",
"x-force-features=on", "check=off", "enforce=off")
* resulting on "-cpu Cascadelake-Server" and the remaining arguments are ignored.
For the example above, one should tag it (or not at all) as "cpu:Cascadelake-Server"
AND self.vm.add_args('-cpu', "Cascadelake-Server,x-force-features=on,check=off,enforce=off"),
and that results on something like:
"qemu-system-x86_64 (...) -cpu Cascadelake-Server -cpu Cascadelake-Server,x-force-features=on,check=off,enforce=off".
QEMU is going to ignore the first -cpu argument. See the patch 0003 for a reference.
This series was tested on CI (https://gitlab.com/wainersm/qemu/-/pipelines/261254251)
and with the following code:
from avocado_qemu import Test
class CPUTest(Test):
def test_cpu(self):
"""
:avocado: tags=cpu:host
"""
# The cpu property is set to the tag value, or None on its absence
self.assertEqual(self.cpu, "host")
# The created VM has the '-cpu host' option
self.assertIn("-cpu host", " ".join(self.vm._args))
self.vm.launch()
def test_cpu_none(self):
self.assertEqual(self.cpu, None)
self.assertNotIn('-cpu', self.vm._args)
Wainer dos Santos Moschetta (3):
tests/acceptance: Automatic set -cpu to the test vm
tests/acceptance: Let the framework handle "cpu:VALUE" tagged tests
tests/acceptance: Tagging tests with "cpu:VALUE"
docs/devel/testing.rst | 8 ++++++++
tests/acceptance/avocado_qemu/__init__.py | 4 ++++
tests/acceptance/boot_linux.py | 3 ---
tests/acceptance/boot_linux_console.py | 16 +++++++++-------
tests/acceptance/machine_mips_malta.py | 7 +++----
tests/acceptance/pc_cpu_hotplug_props.py | 2 +-
tests/acceptance/replay_kernel.py | 17 +++++++++--------
tests/acceptance/reverse_debugging.py | 2 +-
tests/acceptance/tcg_plugins.py | 15 +++++++--------
tests/acceptance/virtio-gpu.py | 4 ++--
tests/acceptance/x86_cpu_model_versions.py | 8 ++++++++
11 files changed, 52 insertions(+), 34 deletions(-)
--
2.29.2
next reply other threads:[~2021-02-24 21:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 21:26 Wainer dos Santos Moschetta [this message]
2021-02-24 21:26 ` [PATCH 1/3] tests/acceptance: Automatic set -cpu to the test vm Wainer dos Santos Moschetta
2021-03-09 18:40 ` Cleber Rosa
2021-02-24 21:26 ` [PATCH 2/3] tests/acceptance: Let the framework handle "cpu:VALUE" tagged tests Wainer dos Santos Moschetta
2021-03-09 19:04 ` Cleber Rosa
2021-02-24 21:26 ` [PATCH 3/3] tests/acceptance: Tagging tests with "cpu:VALUE" Wainer dos Santos Moschetta
2021-03-09 19:18 ` Cleber Rosa
2021-03-09 18:52 ` [PATCH 0/3] tests/acceptance: Handle tests with "cpu" tag Cleber Rosa
2021-03-17 19:16 ` Wainer dos Santos Moschetta
2021-03-23 21:01 ` John Snow
2021-04-07 20:01 ` Eduardo Habkost
2021-04-09 14:53 ` Wainer dos Santos Moschetta
2021-05-14 19:36 ` John Snow
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=20210224212654.1146167-1-wainersm@redhat.com \
--to=wainersm@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=crosa@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wrampazz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.