From: Fam Zheng <famz@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Eric Blake" <eblake@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/3] docker: Add test-block
Date: Fri, 1 Sep 2017 15:06:38 +0800 [thread overview]
Message-ID: <20170901070638.GB4330@lemon.lan> (raw)
In-Reply-To: <1f59ff98-f5cb-b185-bca1-657ed6e2f807@amsat.org>
On Thu, 08/31 13:36, Philippe Mathieu-Daudé wrote:
> On 08/31/2017 01:21 PM, Eric Blake wrote:
> > On 08/31/2017 11:18 AM, Daniel P. Berrange wrote:
> > >
> > > 'qcow' (v1) was also passing last time I checked, though it is
> > > waaaaaay slow to run compared to qcow2, so I'd understand if you
> > > were reluctant to turn that on due to speed
> >
> > Even './check -qcow -g quick' might be nicer than nothing, but that is
> > also slooooooow
>
> What about having a daily job running it on /master? Better than running it
> once before each release :)
>
Can Shippable or Travis cover that?
Fam
next prev parent reply other threads:[~2017-09-01 7:06 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
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 [this message]
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=20170901070638.GB4330@lemon.lan \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.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 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.