From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH] .gitlab-ci.d/crossbuilds.yml: Force 'make check' to -j2 for cross-i686-tci
Date: Tue, 17 Sep 2024 08:01:19 +0200 [thread overview]
Message-ID: <83c88cdd-85ba-482b-ad15-253f2ef913f8@redhat.com> (raw)
In-Reply-To: <20240916134913.2540486-1-peter.maydell@linaro.org>
On 16/09/2024 15.49, Peter Maydell wrote:
> In commit 1374ed49e1453c300 we forced the cross-i686-tci job to -j1 to
> see if this helped with test timeouts. It seems to help with that but
> on the other hand we now sometimes run into the overall 60 minute
> job timeout. Try -j2 instead.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> .gitlab-ci.d/crossbuilds.yml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml
> index 1e21d082aa4..95dfc392244 100644
> --- a/.gitlab-ci.d/crossbuilds.yml
> +++ b/.gitlab-ci.d/crossbuilds.yml
> @@ -62,11 +62,11 @@ cross-i686-tci:
> IMAGE: debian-i686-cross
> ACCEL: tcg-interpreter
> EXTRA_CONFIGURE_OPTS: --target-list=i386-softmmu,i386-linux-user,aarch64-softmmu,aarch64-linux-user,ppc-softmmu,ppc-linux-user --disable-plugins --disable-kvm
> - # Force tests to run in series, to see whether this
> + # Force tests to run with reduced parallelism, to see whether this
> # reduces the flakiness of this CI job. The CI
> # environment by default shows us 8 CPUs and so we
> # would otherwise be using a parallelism of 9.
> - MAKE_CHECK_ARGS: check check-tcg -j1
> + MAKE_CHECK_ARGS: check check-tcg -j2
>
> cross-mipsel-system:
> extends: .cross_system_build_job
Reviewed-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2024-09-17 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 13:49 [PATCH] .gitlab-ci.d/crossbuilds.yml: Force 'make check' to -j2 for cross-i686-tci Peter Maydell
2024-09-17 6:01 ` Thomas Huth [this message]
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=83c88cdd-85ba-482b-ad15-253f2ef913f8@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--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).