Alex Bennée <alex.ben...@linaro.org> writes:
> A significant portion of our CI logs are just enumerating each > successfully built object file. The current widespread versions of > ninja don't have a quiet option so we use NINJA_STATUS to add a fixed > string to the ninja output which we then filter with fgrep. If there > are any errors in the output we get them from the compiler. > > Signed-off-by: Alex Bennée <alex.ben...@linaro.org> > --- > .gitlab-ci.d/buildtest-template.yml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/.gitlab-ci.d/buildtest-template.yml > b/.gitlab-ci.d/buildtest-template.yml > index 73ecfabb8d..3c4b237e4f 100644 > --- a/.gitlab-ci.d/buildtest-template.yml > +++ b/.gitlab-ci.d/buildtest-template.yml > @@ -21,7 +21,7 @@ > then > ../meson/meson.py configure . -Dbackend_max_links="$LD_JOBS" ; > fi || exit 1; > - - make -j"$JOBS" > + - 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? -- Alex Bennée Virtualisation Tech Lead @ Linaro
