From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org,
Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
Subject: Re: [PATCH] docs/devel/testing: iotests check script should be run via 'run'
Date: Thu, 5 Nov 2026 09:34:33 +0000 [thread overview]
Message-ID: <auxNqQU1SePuiQuq@redhat.com> (raw)
In-Reply-To: <87o6c685ph.fsf@draig.linaro.org>
On Tue, Nov 03, 2026 at 12:22:50PM +0000, Alex Bennée wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > 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
> >
> > Update the documentation to match this.
> >
> > Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> > ---
> > docs/devel/testing/main.rst | 14 +++++++++-----
> > 1 file changed, 9 insertions(+), 5 deletions(-)
> >
> > diff --git a/docs/devel/testing/main.rst b/docs/devel/testing/main.rst
> > index b0ca37fe2ba..e26b8af0c79 100644
> > --- a/docs/devel/testing/main.rst
> > +++ b/docs/devel/testing/main.rst
> > @@ -272,8 +272,12 @@ scripts. The testing success criteria is golden output comparison, and the
> > test files are named with numbers.
> >
> > To run iotests, make sure QEMU is built successfully, then switch to the
> > -``tests/qemu-iotests`` directory under the build directory, and run ``./check``
> > -with desired arguments from there.
> > +``tests/qemu-iotests`` directory under the build directory, and run
> > +the ``check`` script via the ``run`` wrapper which sets up the environment:
> > +
> > +.. code::
> > +
> > + ../../run ./check [args]
> >
>
> This is possibly a personal preference thing but is there actually a
> reason for cwd to be tests/qemu-iotests or should we frame it as:
>
> $BLD/run tests/qemu-iotests/check
>
> which is how the functional tests are listed?
For the sake of docs it is probably a good idea to be run consistent
and illustrate use of 'run' from the root of the build dir ie
./run tests/qemu-iotests/check
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 :|
next prev parent reply other threads:[~2026-11-05 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 11:08 [PATCH] docs/devel/testing: iotests check script should be run via 'run' Peter Maydell
2026-11-03 12:22 ` Alex Bennée
2026-11-03 13:26 ` Peter Maydell
2026-11-05 9:34 ` Daniel P. Berrangé [this message]
2026-11-05 10:20 ` Peter Maydell
2026-11-05 10:25 ` Daniel P. Berrangé
2026-11-05 8:16 ` Pierrick Bouvier
2026-11-05 9:25 ` Peter Maydell
2026-11-05 9:32 ` Daniel P. Berrangé
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=auxNqQU1SePuiQuq@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--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.