From: "Daniel P. Berrange" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: "Eric Blake" <eblake@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH v2 3/3] docker: Add test-block
Date: Fri, 1 Sep 2017 11:07:36 +0100 [thread overview]
Message-ID: <20170901100736.GH31680@redhat.com> (raw)
In-Reply-To: <20170901095552.GE4330@lemon.lan>
On Fri, Sep 01, 2017 at 05:55:52PM +0800, Fam Zheng wrote:
> On Thu, 08/31 11:06, Eric Blake wrote:
> > On 08/31/2017 06:22 AM, Fam Zheng wrote:
> > > Signed-off-by: Fam Zheng <famz@redhat.com>
> > > ---
> > > tests/docker/test-block | 21 +++++++++++++++++++++
> > > 1 file changed, 21 insertions(+)
> > > create mode 100755 tests/docker/test-block
> >
> >
> > > +cd "$BUILD_DIR"
> > > +
> > > +build_qemu --target-list=x86_64-softmmu
> > > +cd tests/qemu-iotests
> > > +./check -raw
> > > +./check -qcow2
> >
> > Should we also run ./check -nbd?
>
> Yes, I can add it, and -g quick to all formats, so that the whole test is not
> lagged too badly, and that writing "quick" tests is encouraged in some degree.
If you also add a "daily" test, you could make the daily one run all tests,
while the per-commit one just uses 'quick'.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-09-01 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 11:22 [Qemu-devel] [PATCH v2 0/3] docker: Add test-block Fam Zheng
2017-08-31 11:22 ` [Qemu-devel] [PATCH v2 1/3] docker: Use unconfined security profile Fam Zheng
2017-08-31 11:22 ` [Qemu-devel] [PATCH v2 2/3] docker: Add nettle-devel to fedora image Fam Zheng
2017-08-31 11:22 ` [Qemu-devel] [PATCH v2 3/3] docker: Add test-block Fam Zheng
2017-08-31 16:06 ` Eric Blake
2017-08-31 16:31 ` Kashyap Chamarthy
2017-09-01 9:55 ` Fam Zheng
2017-09-01 10:07 ` Daniel P. Berrange [this message]
2017-08-31 16:18 ` Daniel P. Berrange
2017-08-31 16:21 ` Eric Blake
2017-08-31 16:36 ` Philippe Mathieu-Daudé
2017-09-01 7:06 ` Fam Zheng
2017-09-01 8:22 ` Fam Zheng
2017-09-01 9:22 ` Daniel P. Berrange
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=20170901100736.GH31680@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.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 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).