From: Fam Zheng <famz@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: John Snow <jsnow@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH RFC] tests: Run qtest cases in parallel
Date: Fri, 23 Sep 2016 17:59:05 +0800 [thread overview]
Message-ID: <20160923095905.GJ8832@lemon> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020B03D674C@SZXEMA503-MBS.china.huawei.com>
On Fri, 09/23 09:39, Gonglei (Arei) wrote:
>
> Hi Fam,
>
>
> > -----Original Message-----
> > From: Qemu-devel
> > [mailto:qemu-devel-bounces+arei.gonglei=huawei.com@nongnu.org] On
> > Behalf Of Fam Zheng
> > Sent: Friday, September 23, 2016 3:58 PM
> > To: John Snow
> > Cc: pbonzini@redhat.com; qemu-devel@nongnu.org
> > Subject: Re: [Qemu-devel] [PATCH RFC] tests: Run qtest cases in parallel
> >
> > On Wed, 09/21 14:24, John Snow wrote:
> > >
> > >
> > > On 08/12/2016 05:19 AM, Fam Zheng wrote:
> > > > Previously all test cases in a category, such as check-qtest-y, are
> > > > executed in a single long gtester command. This patch separates each
> > > > test into its own make target to allow better parallism.
> > > >
>
> That's will be great if we can specify a test to run, especially for the scenario
> which add one use qtest case.
>
> For example:
>
> # make check test-crypto-cipher
>
> then only run the tests/ test-crypto-cipher.
>
> Do you think it makes sense?
Or more likely:
# make check TESTS="test-crypto-cipher test-crypto-hash ..."
Usually I just extract the gtester command line with V=1 and run it from my
shell prompt. Feel free to send a patch, though.
Fam
next prev parent reply other threads:[~2016-09-23 9:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 9:19 [Qemu-devel] [PATCH RFC] tests: Run qtest cases in parallel Fam Zheng
2016-09-21 18:24 ` John Snow
2016-09-23 7:58 ` Fam Zheng
2016-09-23 9:39 ` Gonglei (Arei)
2016-09-23 9:59 ` Fam Zheng [this message]
2016-09-24 2:37 ` Gonglei (Arei)
2016-09-27 10:14 ` Daniel P. Berrange
2016-09-28 1:31 ` Gonglei (Arei)
2016-09-28 1:45 ` Fam Zheng
2016-09-28 1:54 ` Gonglei (Arei)
2016-09-28 2:10 ` Fam Zheng
2016-09-27 10:17 ` Daniel P. Berrange
2016-09-27 10:58 ` 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=20160923095905.GJ8832@lemon \
--to=famz@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=jsnow@redhat.com \
--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).