From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Andrew Jones" <drjones@redhat.com>,
peterx@redhat.com, "Radim Krčmář" <rkrcmar@redhat.com>
Subject: [Qemu-devel] [kvm-unit-tests PATCH v3 0/2] run_tests: support concurrent test execution
Date: Fri, 6 Jan 2017 11:32:59 +0800 [thread overview]
Message-ID: <1483673581-7843-1-git-send-email-peterx@redhat.com> (raw)
v3:
- better handling for ctrl-c during run_tests.sh [Radim]
v2:
- patch 1: do per-test logging in all cases
- patch 2: throw away task.bash, instead, take Radim's suggestion to
use jobs
run_tests.sh is getting slower. Maybe it's time to let it run faster.
An obvious issue is that, we were running the tests sequentially in
the past.
This series provides another new "-j" parameter. "-j 8" means we run
the tests on 8 task queues. That'll fasten the script a lot. A very
quick test of mine shows 3x speed boost with 8 task queues.
Please review, thanks.
Peter Xu (2):
run_tests: put logs into per-test file
run_tests: allow run tests in parallel
Makefile | 4 ++--
run_tests.sh | 26 ++++++++++++++++++--------
scripts/functions.bash | 26 ++++++++++++++++++++++++--
scripts/global.bash | 13 +++++++++++++
4 files changed, 57 insertions(+), 12 deletions(-)
create mode 100644 scripts/global.bash
--
2.7.4
next reply other threads:[~2017-01-06 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 3:32 Peter Xu [this message]
2017-01-06 3:33 ` [Qemu-devel] [kvm-unit-tests PATCH v3 1/2] run_tests: put logs into per-test file Peter Xu
2017-01-06 13:51 ` Andrew Jones
2017-01-09 3:13 ` Peter Xu
2017-01-06 3:33 ` [Qemu-devel] [kvm-unit-tests PATCH v3 2/2] run_tests: allow run tests in parallel Peter Xu
2017-01-06 14:40 ` Andrew Jones
2017-01-09 3:47 ` Peter Xu
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=1483673581-7843-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@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).