From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/7] iotests: Allow out-of-tree run
Date: Fri, 16 May 2014 16:06:27 +0800 [thread overview]
Message-ID: <20140516080627.GF1941@T430.nay.redhat.com> (raw)
In-Reply-To: <1400192774-606-1-git-send-email-mreitz@redhat.com>
On Fri, 05/16 00:26, Max Reitz wrote:
> This series enables qemu-iotests to be run in a build tree outside of
> the source tree.
Yes, I've always used the long command to run iotests, namely,
$ (cd $SRC_PATH/tests/qemu-iotests; TEST_DIR=/tmp/qemu-iotests QEMU_PROG=~/build/last/x86_64-softmmu/qemu-system-x86_64 QEMU_IMG_PROG=~/build/last/qemu-img QEMU_IO_PROG=~/build/last/qemu-io QEMU_NBD_PROG=~/build/last/qemu-nbd ./check -qcow2 -o "" )
and I hated that. It'd be a great improvement to allow iotests to find the
built binaries by itself.
Thanks for working on this!
Fam
>
>
> Max Reitz (7):
> iotests: Allow out-of-tree run
> configure: Enable out-of-tree iotests
> iotests: Add default common.env
> iotests: Source common.env
> iotests: Use $PYTHON for Python scripts
> iotests: Drop Python version from 065's Shebang
> iotests: Fix 083 for out-of-tree builds
>
> configure | 12 ++++
> tests/qemu-iotests/031 | 8 +--
> tests/qemu-iotests/036 | 6 +-
> tests/qemu-iotests/039 | 18 +++---
> tests/qemu-iotests/054 | 2 +-
> tests/qemu-iotests/060 | 20 +++----
> tests/qemu-iotests/061 | 24 ++++----
> tests/qemu-iotests/065 | 2 +-
> tests/qemu-iotests/083 | 10 ++--
> tests/qemu-iotests/check | 102 ++++++++++++++++++++++++++++++----
> tests/qemu-iotests/common | 8 +--
> tests/qemu-iotests/common.config | 2 +-
> tests/qemu-iotests/common.env.default | 6 ++
> tests/qemu-iotests/common.rc | 8 +--
> tests/qemu-iotests/iotests.py | 3 +-
> 15 files changed, 165 insertions(+), 66 deletions(-)
> create mode 100644 tests/qemu-iotests/common.env.default
>
> --
> 1.9.2
>
>
prev parent reply other threads:[~2014-05-16 8:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 22:26 [Qemu-devel] [PATCH 0/7] iotests: Allow out-of-tree run Max Reitz
2014-05-15 22:26 ` [Qemu-devel] [PATCH 1/7] " Max Reitz
2014-05-15 22:52 ` Eric Blake
2014-05-16 14:43 ` Max Reitz
2014-05-16 15:09 ` Eric Blake
2014-05-16 15:11 ` Max Reitz
2014-05-15 22:26 ` [Qemu-devel] [PATCH 2/7] configure: Enable out-of-tree iotests Max Reitz
2014-05-15 22:26 ` [Qemu-devel] [PATCH 3/7] iotests: Add default common.env Max Reitz
2014-05-15 22:26 ` [Qemu-devel] [PATCH 4/7] iotests: Source common.env Max Reitz
2014-05-16 7:40 ` Fam Zheng
2014-05-16 14:49 ` Max Reitz
2014-05-15 22:26 ` [Qemu-devel] [PATCH 5/7] iotests: Use $PYTHON for Python scripts Max Reitz
2014-05-16 7:54 ` Fam Zheng
2014-05-16 14:52 ` Max Reitz
2014-05-15 22:26 ` [Qemu-devel] [PATCH 6/7] iotests: Drop Python version from 065's Shebang Max Reitz
2014-05-15 22:26 ` [Qemu-devel] [PATCH 7/7] iotests: Fix 083 for out-of-tree builds Max Reitz
2014-05-16 8:06 ` Fam Zheng [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=20140516080627.GF1941@T430.nay.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).