From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Fam Zheng" <fam@euphon.net>,
qemu-block@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [RFC PATCH] ahci-test: Add dependency to qemu-img tool
Date: Mon, 28 Jan 2019 17:08:30 +0100 [thread overview]
Message-ID: <20190128160830.GH5756@localhost.localdomain> (raw)
In-Reply-To: <1c788b0e-6a4b-f04f-b413-e7211fc62e85@redhat.com>
Am 25.01.2019 um 22:57 hat John Snow geschrieben:
> On 1/25/19 3:34 PM, Philippe Mathieu-Daudé wrote:
> > Since the ahci-test uses qemu-img, add a dependency to build it
> > before using it.
> > This fixes:
> >
> > $ gmake check-qtest V=1
> > QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/ahci-test
> > Failed to execute child process "/tmp/qemu-test.19tMRF/qemu-img" (No such file or directory)
> > ERROR:tests/libqos/libqos.c:192:mkimg: assertion failed: (ret && !err)
> >
> > Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> > ---
> > RFC because while this dependency is valid, I don't think this is the
> > clever way to solve this problem (which is, assuming the host
> > distribution has the qemu-tools installed).
> > I guess remember a thread about it (Eric, John?) where it was asked
> > "What do we want to test, qemu-img or AHCI? Can we trust an unstable
> > version of a tool to verify a device?"
> >
> [...]
>
> Reviewed-by: John Snow <jsnow@redhat.com>
Are you taking this through your tree, or through which tree should it
be merged?
Kevin
next prev parent reply other threads:[~2019-01-28 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 20:34 [Qemu-devel] [RFC PATCH] ahci-test: Add dependency to qemu-img tool Philippe Mathieu-Daudé
2019-01-25 21:57 ` John Snow
2019-01-28 16:08 ` Kevin Wolf [this message]
2019-01-28 19:14 ` John Snow
2019-01-29 7:03 ` Philippe Mathieu-Daudé
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=20190128160830.GH5756@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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).