From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, Ed Maste <emaste@freebsd.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] qtest: Add assertion that required environment variable is set
Date: Mon, 06 Apr 2015 13:46:15 -0400 [thread overview]
Message-ID: <5522C667.80200@redhat.com> (raw)
In-Reply-To: <CAFEAcA8nyMCnYOAhjfYxJ1q6Ei_04L5Jr2ERrMUQaE+KCqKDRw@mail.gmail.com>
On 04/03/2015 07:18 AM, Peter Maydell wrote:
> On 2 April 2015 at 20:31, Ed Maste <emaste@freebsd.org> wrote:
>> On 1 April 2015 at 18:45, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> Also irritating is the way it silently requires
>>> the binary to have a name in the shape it was
>>> expecting, which can catch you out if you were
>>> trying to set it to a wrapper shell script that
>>> invokes valgrind or something...
>>
>> I don't really have enough context to propose a good user-facing
>> message with a tip for manually executing this, so hopefully someone
>> else can provide one. I just noticed one other instance that already
>> had an assertion on getenv("QTEST_QEMU_BINARY") being non-null.
>
> Yes, that was just me venting about something that caught me
> out in the past rather than review comment on this patch :-)
> Sorry for any confusion.
>
> -- PMM
>
I'll pull this into ide-next for 2.4 -- I have some ahci-test things to
submit anyway.
I'll touch up the user facing error messages in a later patch and hit a
few of the startup assertions all at once.
Thanks.
--js
WARNING: multiple messages have this Message-ID (diff)
From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, Ed Maste <emaste@freebsd.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qtest: Add assertion that required environment variable is set
Date: Mon, 06 Apr 2015 13:46:15 -0400 [thread overview]
Message-ID: <5522C667.80200@redhat.com> (raw)
In-Reply-To: <CAFEAcA8nyMCnYOAhjfYxJ1q6Ei_04L5Jr2ERrMUQaE+KCqKDRw@mail.gmail.com>
On 04/03/2015 07:18 AM, Peter Maydell wrote:
> On 2 April 2015 at 20:31, Ed Maste <emaste@freebsd.org> wrote:
>> On 1 April 2015 at 18:45, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> Also irritating is the way it silently requires
>>> the binary to have a name in the shape it was
>>> expecting, which can catch you out if you were
>>> trying to set it to a wrapper shell script that
>>> invokes valgrind or something...
>>
>> I don't really have enough context to propose a good user-facing
>> message with a tip for manually executing this, so hopefully someone
>> else can provide one. I just noticed one other instance that already
>> had an assertion on getenv("QTEST_QEMU_BINARY") being non-null.
>
> Yes, that was just me venting about something that caught me
> out in the past rather than review comment on this patch :-)
> Sorry for any confusion.
>
> -- PMM
>
I'll pull this into ide-next for 2.4 -- I have some ahci-test things to
submit anyway.
I'll touch up the user facing error messages in a later patch and hit a
few of the startup assertions all at once.
Thanks.
--js
next prev parent reply other threads:[~2015-04-06 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 18:00 [Qemu-trivial] [PATCH] qtest: Add assertion that required environment variable is set Ed Maste
2015-04-01 18:00 ` [Qemu-devel] " Ed Maste
2015-04-01 21:06 ` [Qemu-trivial] " John Snow
2015-04-01 21:06 ` John Snow
2015-04-01 21:14 ` [Qemu-trivial] " Paolo Bonzini
2015-04-01 21:14 ` [Qemu-devel] " Paolo Bonzini
2015-04-01 22:45 ` [Qemu-trivial] " Peter Maydell
2015-04-01 22:45 ` Peter Maydell
2015-04-02 19:31 ` [Qemu-trivial] " Ed Maste
2015-04-02 19:31 ` Ed Maste
2015-04-03 11:18 ` [Qemu-trivial] " Peter Maydell
2015-04-03 11:18 ` Peter Maydell
2015-04-06 17:46 ` John Snow [this message]
2015-04-06 17:46 ` John Snow
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=5522C667.80200@redhat.com \
--to=jsnow@redhat.com \
--cc=emaste@freebsd.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.