From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] cirrus-ci: parallelize "make check"
Date: Wed, 18 Nov 2020 12:49:33 +0000 [thread overview]
Message-ID: <875z62x21u.fsf@linaro.org> (raw)
In-Reply-To: <20201118101821.132236-1-pbonzini@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Otherwise, the tests risk failing due to timeouts.
This is a reversion of what we used to do because it's very hard to
figure out which test broke when they are all mixed together. Maybe we
could just up the timeouts.
That said the timeouts seem a bit random with macos taking around 53
minutes and macos_xcode taking less at around 44 unless they get "stuck".
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> .cirrus.yml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/.cirrus.yml b/.cirrus.yml
> index f0209b7a3e..111e19f1bf 100644
> --- a/.cirrus.yml
> +++ b/.cirrus.yml
> @@ -29,7 +29,7 @@ macos_task:
> --extra-cflags='-Wno-error=deprecated-declarations'
> || { cat config.log meson-logs/meson-log.txt; exit 1; }
> - gmake -j$(sysctl -n hw.ncpu)
> - - gmake check V=1
> + - gmake -j$(sysctl -n hw.ncpu) check V=1
>
> macos_xcode_task:
> osx_instance:
> @@ -43,7 +43,7 @@ macos_xcode_task:
> - ../configure --extra-cflags='-Wno-error=deprecated-declarations' --enable-modules
> --enable-werror --cc=clang || { cat config.log meson-logs/meson-log.txt; exit 1; }
> - gmake -j$(sysctl -n hw.ncpu)
> - - gmake check V=1
> + - gmake -j$(sysctl -n hw.ncpu) check V=1
>
> windows_msys2_task:
> timeout_in: 90m
--
Alex Bennée
next prev parent reply other threads:[~2020-11-18 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 10:18 [PATCH] cirrus-ci: parallelize "make check" Paolo Bonzini
2020-11-18 12:49 ` Alex Bennée [this message]
2020-11-18 13:43 ` 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=875z62x21u.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--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).