From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [RFC PATCH] gitlab: call ninja directly and reduce build noise
Date: Fri, 03 Feb 2023 16:23:54 +0000 [thread overview]
Message-ID: <87k00yk98k.fsf@linaro.org> (raw)
In-Reply-To: <478e4940-ba22-6b70-119a-b7416680db97@linaro.org>
Richard Henderson <richard.henderson@linaro.org> writes:
> On 2/2/23 08:59, Alex Bennée wrote:
>>> + - env NINJA_STATUS="[ninja][%f/%t] " ninja | fgrep -v "[ninja]"
>>> - if test -n "$MAKE_CHECK_ARGS";
>>> then
>>> make -j"$JOBS" $MAKE_CHECK_ARGS ;
>> This is too much for gitlab as it trips up on no output at all. What
>> we
>> really need is something that filters ninja output, counts the lines and
>> outputs a dot every 10? 20? lines to keep gitlab happy.
>> Shonky shell script? Very clever sed?
>
> NINJA_STATUS='ninja %f: ' ninja | grep 'ninja.*[02468]0:'
NINJA_STATUS="[ninja][%f/%t] " ninja | grep -v "\[ninja\]\[.*[123456789]/"
but I guess I need to include it from the Makefile invocation
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-02-03 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 17:59 [RFC PATCH] gitlab: call ninja directly and reduce build noise Alex Bennée
2023-02-02 18:59 ` Alex Bennée
2023-02-02 23:30 ` Richard Henderson
2023-02-03 16:23 ` Alex Bennée [this message]
2023-02-03 7:58 ` Thomas Huth
2023-02-03 8:45 ` Philippe Mathieu-Daudé
2023-02-03 16:28 ` Alex Bennée
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=87k00yk98k.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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.