All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>
Subject: Re: [PATCH v2 for-11.2] docs/devel/testing: iotests check script should be run via 'run'
Date: Wed, 11 Nov 2026 09:14:20 +0000	[thread overview]
Message-ID: <avQx7OOfuoez9Fs6@redhat.com> (raw)
In-Reply-To: <au4uyq1cntUoa7oO@redhat.com>

On Fri, Nov 06, 2026 at 01:55:39PM -0600, Eric Blake wrote:
> On Fri, Nov 06, 2026 at 05:01:57PM +0000, Peter Maydell wrote:
> > The iotests section of the testing documentation suggests directly
> > running the "./check" script.  However if you do this then the
> > script complains:
> > 
> > WARNING: iotests is being run from outside of the configure-time python virtual environment
> > [...]
> > Please use the meson run script:
> >         /home/pm215/qemu/build/x86-tgt-san-dbg/run ./check
> 
> Huh. I did a git checkout, mkdir build, cd build && ../configure, then:
> 
> $ build/run tests/qemu-iotests/check 5
> 
> WARNING: iotests is being run from outside of the configure-time python virtual environment
> 
> current python: /home/eblake/qemu/build/pyvenv/bin/python3
> pyvenv python:  /home/pyvenv/bin/python3
> ...

Beyond that warning, the 'check' script has bad heuristics for
finding the build directory, looking for 'cwd' in this particular
case which is wrong. I've sent a path that addresses this which
does the job in my testing at least.

> but running directly from the configured directory:
> 
> $ cd build
> $ ./run tets/qemu-iotests/check 5
> 
> does what this patch recommends.
> 

With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|



      reply	other threads:[~2026-11-11  9:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 17:01 [PATCH v2 for-11.2] docs/devel/testing: iotests check script should be run via 'run' Peter Maydell
2026-11-06 17:06 ` Daniel P. Berrangé
2026-11-06 17:31 ` Pierrick Bouvier
2026-11-06 19:55 ` Eric Blake
2026-11-11  9:14   ` Daniel P. Berrangé [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=avQx7OOfuoez9Fs6@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=eblake@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pierrick.bouvier@oss.qualcomm.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.