qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/5] docker: Add test-block
Date: Fri, 5 May 2017 16:05:13 +0800	[thread overview]
Message-ID: <20170505080513.GC21435@lemon.lan> (raw)
In-Reply-To: <03beb071-ebbc-4328-3530-37b9856476cc@redhat.com>

On Fri, 05/05 09:44, Paolo Bonzini wrote:
> 
> 
> On 05/05/2017 05:23, Fam Zheng wrote:
> > A few tweaks to the docker images and running commands allow us to run
> > qemu-iotests in the fedora container. This will be added to the patchew test
> > cases later.
> > 
> > Fam Zheng (5):
> >   docker: Run tests with current user
> >   docker: Add bzip2 and hostname to fedora image
> >   docker: Use unconfined security profile
> >   docker: Add libaio to fedora image
> >   docker: Add test-block
> > 
> >  tests/docker/Makefile.include          |  3 ++-
> >  tests/docker/dockerfiles/fedora.docker |  4 ++--
> >  tests/docker/test-block                | 21 +++++++++++++++++++++
> >  3 files changed, 25 insertions(+), 3 deletions(-)
> >  create mode 100755 tests/docker/test-block
> > 
> 
> Patches 1-4:
> 
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> For patch 5, I think we should revive the "quick" qemu-iotests group
> (maybe we can have support for skipping groups, and have a "slow" group
> with the very few tests that take >30 seconds?) and add the quick tests
> to "make check".

Sounds like a good idea, but for a separate series, IMO.

The idea of the new test-block is to include all qemu-iotests tests.  I only
added raw and qcow2 because vmdk etc. fails case 181. I could use "-x" but
that's a bit ugly - they can wait for the fix.

Fam

  reply	other threads:[~2017-05-05  8:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  3:23 [Qemu-devel] [PATCH 0/5] docker: Add test-block Fam Zheng
2017-05-05  3:23 ` [Qemu-devel] [PATCH 1/5] docker: Run tests with current user Fam Zheng
2017-05-05  8:25   ` Alex Bennée
2017-05-06 16:25   ` Philippe Mathieu-Daudé
2017-05-05  3:23 ` [Qemu-devel] [PATCH 2/5] docker: Add bzip2 and hostname to fedora image Fam Zheng
2017-05-05  8:25   ` Alex Bennée
2017-05-06 16:34   ` Philippe Mathieu-Daudé
2017-05-05  3:23 ` [Qemu-devel] [PATCH 3/5] docker: Use unconfined security profile Fam Zheng
2017-05-05  8:27   ` Alex Bennée
2017-05-05  9:12     ` Fam Zheng
2017-05-06 16:33   ` Philippe Mathieu-Daudé
2017-05-05  3:23 ` [Qemu-devel] [PATCH 4/5] docker: Add libaio to fedora image Fam Zheng
2017-05-05  8:27   ` Alex Bennée
2017-05-06 16:26   ` Philippe Mathieu-Daudé
2017-05-05  3:23 ` [Qemu-devel] [PATCH 5/5] docker: Add test-block Fam Zheng
2017-05-05  8:28   ` Alex Bennée
2017-05-05  8:55     ` Fam Zheng
2017-05-08 15:11   ` Yash Mankad
2017-05-08 15:52   ` Daniel P. Berrange
2017-05-05  7:44 ` [Qemu-devel] [PATCH 0/5] " Paolo Bonzini
2017-05-05  8:05   ` Fam Zheng [this message]
2017-05-05  8:07     ` Paolo Bonzini
2017-05-05  8:52       ` Fam Zheng
2017-05-08 15:55   ` Daniel P. Berrange
2017-05-08 16:06     ` Paolo Bonzini

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=20170505080513.GC21435@lemon.lan \
    --to=famz@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@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).