qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Levon <john.levon@nutanix.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
	"Thanos Makatos" <thanos.makatos@nutanix.com>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Mark Cave-Ayland" <mark.caveayland@nutanix.com>
Subject: Re: [PATCH v5] tests/functional: add a vfio-user smoke test
Date: Thu, 11 Sep 2025 18:11:02 +0200	[thread overview]
Message-ID: <aML0libYHIsteYJH@lent> (raw)
In-Reply-To: <0d71919b-d5f9-47cd-9979-a692f3cf6a8d@redhat.com>

On Thu, Sep 11, 2025 at 05:27:24PM +0200, Thomas Huth wrote:

> I'm not a python expert, but I guess it would make sense to move that
> description block next to the "class VfioUserClient(QemuSystemTest):" line
> so that it's the description for the class? (that would fix the "Missing
> class docstring" that you get when using "pylint" on your code)

Then pylint complains about the module missing docs, so I think the current
location is a bit better, and I'll add a single line for the class, and made the
file pylint clean generally.

> > +        # wait for libvfio-user to initialize properly
> > +        exec_command_and_wait_for_pattern(self, 'sleep 5', '#', None, server_vm)
> 
> Could the sleep be avoided? ... it's still a race condition (even if it's
> unlikely when you wait for 5 seconds), and always sleeping 5 seconds slows
> down the test quite a bit ...

Currently stress testing a loop that just waits for the socket to appear, so far
so good.

thanks
john


      parent reply	other threads:[~2025-09-11 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11 14:22 [PATCH v5] tests/functional: add a vfio-user smoke test John Levon
2025-09-11 15:27 ` Thomas Huth
2025-09-11 15:50   ` Daniel P. Berrangé
2025-09-11 16:11   ` John Levon [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=aML0libYHIsteYJH@lent \
    --to=john.levon@nutanix.com \
    --cc=berrange@redhat.com \
    --cc=clg@redhat.com \
    --cc=mark.caveayland@nutanix.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thanos.makatos@nutanix.com \
    --cc=thuth@redhat.com \
    --cc=zhao1.liu@intel.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).