From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, famz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] docker: allow running "docker-travis" with arbitrary parallelism
Date: Fri, 14 Jul 2017 12:38:13 +0200 [thread overview]
Message-ID: <52b9202e-7ad1-e7f8-e916-0f63f9d9b959@redhat.com> (raw)
In-Reply-To: <87shhzuye8.fsf@linaro.org>
On 14/07/2017 12:05, Alex Bennée wrote:
>
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
>> docker-travis is limited to the -j3 flag specified for running on the
>> SaaS Travis CI infrastructure.
>>
>> When running the test matrix locally with docker, however, we can run
>> much more jobs at the same time on a suitably beefy server. Let people
>> do that with the usual J=nn option already supported by the other
>> docker-based tests.
>
> Eh, I was debugging stuff on our beefy server with J=20 and then I
> realised I was just running:
>
> make docker-test-quick@travis J=20
>
> So I guess some people do use the pseudo Travis expansion then?
How would that end up running tests/docker/travis?
Paolo
>>
>> Paolo
>>
>> Paolo Bonzini (2):
>> docker: allow customizing Travis global_env variables
>> travis: move make -j flag out of script
>>
>> .travis.yml | 3 ++-
>> tests/docker/travis.py | 6 +++---
>> 2 files changed, 5 insertions(+), 4 deletions(-)
>
>
> --
> Alex Bennée
>
next prev parent reply other threads:[~2017-07-14 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 9:34 [Qemu-devel] [PATCH 0/2] docker: allow running "docker-travis" with arbitrary parallelism Paolo Bonzini
2017-07-14 9:34 ` [Qemu-devel] [PATCH 1/2] docker: allow customizing Travis global_env variables Paolo Bonzini
2017-07-14 9:34 ` [Qemu-devel] [PATCH 2/2] travis: move make -j flag out of script Paolo Bonzini
2017-07-14 10:05 ` [Qemu-devel] [PATCH 0/2] docker: allow running "docker-travis" with arbitrary parallelism Alex Bennée
2017-07-14 10:38 ` Paolo Bonzini [this message]
2017-07-14 13:56 ` Alex Bennée
2017-07-14 14:52 ` 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=52b9202e-7ad1-e7f8-e916-0f63f9d9b959@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=famz@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).