All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] tests/functional: Set 'pc' machine type instead of relying on the default
Date: Thu, 22 May 2025 10:15:28 +0200	[thread overview]
Message-ID: <ca409e44-ea4e-4208-b558-06b42c757567@redhat.com> (raw)
In-Reply-To: <aC3woEjL0UxXYavt@redhat.com>

On 21/05/2025 17.26, Daniel P. Berrangé wrote:
> On Wed, May 21, 2025 at 05:13:23PM +0200, Thomas Huth wrote:
>> From: Thomas Huth <thuth@redhat.com>
>>
>> In case the default machine has not been compiled into the QEMU
>> binary, the vnc and the cpu_hotplug_props test are currently
>> failing. Add a set_machine('pc') here to make sure that the tests
>> are correctly skipped in case the machine is not available.
> 
> Hmmm, this is making this test be tied exclusively to x86.
> If we can't ever omit the machine, then effectively all
> our tests have to be tied to a specific target arch ?

Since you never can rely on the availability of a default machine (there are 
also some targets like arm that don't have a default machine), you either 
have to set a certain machine explicitly with set_machine(), or use the 
"none" machine (if possible). Speaking of the latter - that's maybe a better 
option for this test, so I'll give that a try.

> What scenario did you find that 'pc' wasn't compiled
> into QEMU  x86 targets ?

Run "configure" with "--without-default-devices".

> Shouldn't a new default
> machine have been picked, or should our test harness
> be picking a default for each targets if no 'set_machine'
> call is present, to preserve target portability ?

We're using something like that in select_machine() in 
tests/functional/test_migration.py already ... we could maybe give it a try 
to turn that into a generic function of the qemu_test module, but I guess 
it's hard to find a default for each and every target that satisfies all the 
needs...

  Thomas



      reply	other threads:[~2025-05-22  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21 15:13 [PATCH] tests/functional: Set 'pc' machine type instead of relying on the default Thomas Huth
2025-05-21 15:26 ` Daniel P. Berrangé
2025-05-22  8:15   ` Thomas Huth [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=ca409e44-ea4e-4208-b558-06b42c757567@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.