Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vincent Stehlé" <vincent.stehle@arm.com>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] utils/brmake: filter output for parallel build
Date: Mon, 13 Oct 2025 20:04:25 +0200	[thread overview]
Message-ID: <aO0_KQPauWkz8Cye@debian> (raw)
In-Reply-To: <1148a6fa-9de0-444f-9a4e-d6a91c598dc3@bubu1.eu>

On Fri, Oct 10, 2025 at 03:47:32PM +0200, Marcus Hoffmann via buildroot wrote:
(grep --line-buffered option)
> Ah, this makes sense, I think I have notices this delay here mostly in CI,
> where sometimes there's no output for minutes. This seems to improve that.

Hi Marcus,

This change of behaviour in your CI messages output rate is an unexpected side
effect!

I think that without any option, grep and sed adapt their output buffering
policy automatically in the same way, depending on what they are connected to (a
terminal or something else).

Now that sed is the last program in the pipeline, I would expect that it would
still buffer its output in your CI case, as grep was doing.

If you fancy, you could try to add the "--unbuffered" option to sed command line
and see if that changes its behaviour in your CI:

  |sed --unbuffered -E 's/^([0-9T:-]{19}) [[:print:]]*(.*>>> )/\1 \2/'

> 
> This should probably mentioned in the commit message.

The intention was to avoid any visible change in term of buffering; sed should
have replaced grep in that sense.

Best regards,
Vincent.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-10-13 18:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 15:28 [Buildroot] [PATCH] utils/brmake: filter output for parallel build Vincent Stehlé
2025-10-09 17:42 ` Marcus Hoffmann via buildroot
2025-10-10  8:01   ` Vincent Stehlé
2025-10-10 13:47     ` Marcus Hoffmann via buildroot
2025-10-13 18:04       ` Vincent Stehlé [this message]
2025-10-17 13:49         ` Marcus Hoffmann via buildroot
2025-10-10 13:48 ` Marcus Hoffmann via buildroot
2025-10-17 14:12 ` Marcus Hoffmann via buildroot
2025-10-17 14:39   ` Vincent Stehlé
2025-10-17 15:08     ` Yann E. MORIN via buildroot

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=aO0_KQPauWkz8Cye@debian \
    --to=vincent.stehle@arm.com \
    --cc=buildroot@bubu1.eu \
    --cc=buildroot@buildroot.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