From: Cleber Rosa <crosa@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: philmd@redhat.com, ehabkost@redhat.com,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RESEND PATCH] tests/acceptance: Specify arch for QueryCPUModelExpansion
Date: Wed, 18 Sep 2019 21:25:42 -0400 [thread overview]
Message-ID: <20190919012542.GC23168@localhost.localdomain> (raw)
In-Reply-To: <20190918070654.19356-1-david@gibson.dropbear.id.au>
On Wed, Sep 18, 2019 at 05:06:54PM +1000, David Gibson wrote:
> At the moment this test runs on whatever the host arch is. But it looks
> for 'unavailable-features' which is an x86 specific cpu property. Tag it
> to always use qemu-system-x86_64.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
> ---
> tests/acceptance/cpu_queries.py | 3 +++
> 1 file changed, 3 insertions(+)
>
> I sent this a while back, but it seems to have been forgotten. As far
> as I can tell the current logic is Just Plain Wrong, on any host other
> than x86.
>
> diff --git a/tests/acceptance/cpu_queries.py b/tests/acceptance/cpu_queries.py
> index e71edec39f..af47d2795a 100644
> --- a/tests/acceptance/cpu_queries.py
> +++ b/tests/acceptance/cpu_queries.py
> @@ -18,6 +18,9 @@ class QueryCPUModelExpansion(Test):
> """
>
> def test(self):
> + """
> + :avocado: tags=arch:x86_64
> + """
> self.vm.set_machine('none')
> self.vm.add_args('-S')
> self.vm.launch()
> --
> 2.21.0
>
I've queued on my python-next branch.
Reviewed-by: Cleber Rosa <crosa@redhat.com>
prev parent reply other threads:[~2019-09-19 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 7:06 [Qemu-devel] [RESEND PATCH] tests/acceptance: Specify arch for QueryCPUModelExpansion David Gibson
2019-09-18 11:17 ` Philippe Mathieu-Daudé
2019-09-19 1:25 ` Cleber Rosa [this message]
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=20190919012542.GC23168@localhost.localdomain \
--to=crosa@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@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).