From: Fam Zheng <famz@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Laurent Vivier" <lvivier@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Lukáš Doktor" <ldoktor@redhat.com>
Subject: Re: [Qemu-devel] make check speed
Date: Wed, 23 Aug 2017 16:52:19 +0800 [thread overview]
Message-ID: <20170823085219.GA16292@lemon> (raw)
In-Reply-To: <0bb344a3-f8f8-3365-cef1-1c68cf7d160d@redhat.com>
On Wed, 08/23 10:35, Thomas Huth wrote:
> Is it safe nowadays to run "make check -j4" for example? Last time I
> tried (maybe 1 or 2 years ago), there were still issues since some tests
> were using hard-coded temporary file names, so the parallel tests were
> disturbing each other, for example...
We really should fix them.
Last year I wanted to get some speed up in patchew's "make check" jobs so I
tried this:
https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg07713.html
On my laptop it can save 50% time as shown in the commit message, unfortunately
the patch didn't get enough traction, and I've since then rarely used -j in
"make check" command lines (what?!).
Fam
next prev parent reply other threads:[~2017-08-23 8:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 8:26 [Qemu-devel] [PATCH for-2.10] boot-serial-test: prefer tcg accelerator Cornelia Huck
2017-08-16 8:28 ` Laurent Vivier
2017-08-16 10:25 ` Thomas Huth
2017-08-16 10:51 ` Paolo Bonzini
2017-08-16 11:18 ` Peter Maydell
2017-08-16 11:46 ` Cornelia Huck
2017-08-22 1:09 ` David Gibson
2017-08-22 5:40 ` Thomas Huth
2017-08-22 8:47 ` Peter Maydell
2017-08-22 8:49 ` Laurent Vivier
2017-08-22 9:35 ` Peter Maydell
2017-08-22 11:20 ` David Gibson
2017-08-22 11:48 ` Cornelia Huck
2017-08-23 0:29 ` David Gibson
2017-08-23 7:16 ` Cornelia Huck
2017-08-23 7:49 ` [Qemu-devel] make check speed (was: Re: [PATCH for-2.10] boot-serial-test: prefer tcg accelerator) Thomas Huth
2017-08-23 8:01 ` [Qemu-devel] make check speed Paolo Bonzini
2017-08-23 8:35 ` Thomas Huth
2017-08-23 8:52 ` Fam Zheng [this message]
2017-08-23 9:09 ` Fam Zheng
2017-08-23 9:33 ` Paolo Bonzini
2017-08-24 3:01 ` David Gibson
2017-08-23 11:51 ` Lukáš Doktor
2017-08-23 12:01 ` Thomas Huth
2017-08-23 12:13 ` Lukáš Doktor
2017-08-24 13:52 ` Cleber Rosa
2017-08-23 12:35 ` Thomas Huth
2017-08-23 12:52 ` Lukáš Doktor
2017-08-23 12:20 ` Cornelia Huck
2017-08-24 5:27 ` Thomas Huth
2017-08-30 8:59 ` Cornelia Huck
2017-08-30 9:13 ` Thomas Huth
2017-08-30 11:52 ` Markus Armbruster
2017-08-30 13:56 ` Thomas Huth
2017-08-30 14:19 ` Markus Armbruster
2017-08-29 16:34 ` Thomas Huth
2017-08-29 17:13 ` Thomas Huth
2017-08-16 14:03 ` [Qemu-devel] [PATCH for-2.10] boot-serial-test: prefer tcg accelerator Richard Henderson
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=20170823085219.GA16292@lemon \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=crosa@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=f4bug@amsat.org \
--cc=ldoktor@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@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 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.