From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Beraldo Leal <bleal@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH] gitlab-ci: split clang-user to avoid timeout
Date: Fri, 04 Nov 2022 13:33:02 +0000 [thread overview]
Message-ID: <87fseykfnq.fsf@linaro.org> (raw)
In-Reply-To: <7a67e04a-d723-95e6-0575-1a5a8786d54e@linaro.org>
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 4/11/22 07:27, Thomas Huth wrote:
>> On 03/11/2022 22.23, Stefan Hajnoczi wrote:
>>> GitLab CI times out when the clang-user job takes over 1 hour.
>> Oh, that's new to me ... is that a regression? Has something become
>> slower? Or did we just add more stuff to the user builds recently?
>
> We added more TCG tests:
>
> $ git diff --stat v7.1.0.. -- tests/tcg/
> tests/tcg/Makefile.target | 36 +-
<snip>
but are any of them particularly slow? tcg tests are generally quick (or
at least should be).
>
> Also more s390x tests are going to be merged soon.
>
>> Anyway, if it's just taking a little bit longer than 1h, it's likely
>> better to bump the timeout by 10 minutes (to 70 minutes), I guess
>> that will still take less CI minutes to run than to have two jobs.
>> Thomas
>>
--
Alex Bennée
prev parent reply other threads:[~2022-11-04 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 21:23 [PATCH] gitlab-ci: split clang-user to avoid timeout Stefan Hajnoczi
2022-11-03 22:32 ` Philippe Mathieu-Daudé
2022-11-03 22:45 ` Richard Henderson
2022-11-04 6:27 ` Thomas Huth
2022-11-04 9:32 ` Philippe Mathieu-Daudé
2022-11-04 13:33 ` Alex Bennée [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=87fseykfnq.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=laurent@vivier.eu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@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.