From: Max Reitz <mreitz@redhat.com>
To: Fam Zheng <famz@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 4/7] iotests: Source common.env
Date: Fri, 16 May 2014 16:49:00 +0200 [thread overview]
Message-ID: <5376255C.1040804@redhat.com> (raw)
In-Reply-To: <20140516074008.GD1941@T430.nay.redhat.com>
On 16.05.2014 09:40, Fam Zheng wrote:
> On Fri, 05/16 00:26, Max Reitz wrote:
>> Source common.env in the iotests' check script. If the one supposed to
>> be created by configure cannot be found, use common.env.default from the
>> source tree.
> If configure is supposed to create common.env, but we can't find it here, isn't
> it a bug of configure? If so, I don't think we need common.env.default, we need
> an error.
In fact, I am getting an error. The first . "$configured_common_env"
will print an error message, so the user should be informed of something
going wrong.
You are right in that this should not happen. However, it may happen if
the user decides to run the iotests from the source tree instead of the
build tree if he/she is still used to the old way of invoking them. So I
think, having a default common.env should solve this without creating
new problems.
Max
> Thanks,
> Fam
>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> tests/qemu-iotests/check | 17 +++++++++++++++++
>> 1 file changed, 17 insertions(+)
>>
>> diff --git a/tests/qemu-iotests/check b/tests/qemu-iotests/check
>> index a8d9569..bd66630 100755
>> --- a/tests/qemu-iotests/check
>> +++ b/tests/qemu-iotests/check
>> @@ -89,6 +89,23 @@ then
>> fi
>> fi
>>
>> +# we need common.env
>> +if [ -n "$build_iotests" ]
>> +then
>> + configured_common_env="$build_iotests/common.env"
>> +else
>> + configured_common_env="$source_iotests/common.env"
>> +fi
>> +
>> +if ! . "$configured_common_env"
>> +then
>> + if ! . "$source_iotests/common.env.default"
>> + then
>> + echo "$iam: failed to source common.env"
>> + exit 1
>> + fi
>> +fi
>> +
>> # we need common.config
>> if ! . "$source_iotests/common.config"
>> then
>> --
>> 1.9.2
>>
>>
next prev parent reply other threads:[~2014-05-16 14:49 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 [this message]
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 ` [Qemu-devel] [PATCH 0/7] iotests: Allow out-of-tree run Fam Zheng
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=5376255C.1040804@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@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).