From: Fam Zheng <famz@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] What tests should "make check-block" run?
Date: Fri, 22 Aug 2014 13:01:43 +0800 [thread overview]
Message-ID: <20140822050143.GG3410@T430.redhat.com> (raw)
In-Reply-To: <CAEgOgz4TNhWcpgVqV-dym83XATET2ho+BFw0r0_ZYy__o97urA@mail.gmail.com>
On Thu, 08/21 23:00, Peter Crosthwaite wrote:
> On Thu, Aug 21, 2014 at 10:52 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > Il 21/08/2014 14:27, Markus Armbruster ha scritto:
> >> Current "make check-block" runs tests/qemu-iotests-quick.sh, which tests
> >> format qcow2, protocol file, group quick with cache=none. Runs 55 tests
> >> and takes about 2 minutes for me on a not particularly fast test box
> >> (spinning rust).
> >
> > Perhaps "make check" should run these quick tests, while "make
> > check-block" should run a bigger testsuite.
> >
>
> Is there a make check-foo target to test absolutely everything
> possible? Sometimes when you have far-reaching changes it might be
> good to run an everything test case as an overnighter rather than
> having to think hard about which test suites are relevant to you.
>
I second that. It will be nice to have a make check-full.
Fam
next prev parent reply other threads:[~2014-08-22 5:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 12:27 [Qemu-devel] What tests should "make check-block" run? Markus Armbruster
2014-08-21 12:52 ` Paolo Bonzini
2014-08-21 13:00 ` Peter Crosthwaite
2014-08-22 5:01 ` Fam Zheng [this message]
2014-08-21 14:38 ` Kevin Wolf
2014-08-21 13:12 ` Stefan Hajnoczi
2014-08-21 13:16 ` Peter Maydell
2014-08-28 11:05 ` Stefan Hajnoczi
2014-08-28 15:22 ` Jeff Cody
2014-08-28 15:24 ` Markus Armbruster
2014-08-28 16:19 ` Peter Maydell
2014-08-29 20:05 ` Max Reitz
2014-09-01 7:55 ` Markus Armbruster
2014-08-28 23:50 ` Fam Zheng
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=20140822050143.GG3410@T430.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).