From: "Vincent Stehlé" <vincent.stehle@arm.com>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: buildroot@buildroot.org, "Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH] utils/brmake: filter output for parallel build
Date: Fri, 17 Oct 2025 16:39:54 +0200 [thread overview]
Message-ID: <aPJVOlZTJvdk65L8@debian> (raw)
In-Reply-To: <a4c335e6-b2e3-487d-b6d8-60318059b195@bubu1.eu>
On Fri, Oct 17, 2025 at 04:12:34PM +0200, Marcus Hoffmann wrote:
> Hi Vincent,
..
> After testing this change for a few days now, I have two slightly odd things
> to report:
>
> I have seen the following thing happen once during a CI run, where 2 of the
> lines where truncated in the middle of the timestamp. I have looked through
> a bunch of build logs now but haven't seen this again, so not sure if that's
> an actual problem we need to care about
>
> 2025-10-14T10:28:01 >>> [something]
> 202
> 2025-10-14T10:28:01 >>> [more things]
> [... lots of stuff in between]
> 2025-10-1
>
>
> And secondly, also in CI:
> The "Done in Xmin Ys" text that is printed in the end is still always
> displayed in the middle of a line during the end of the build output:
>
> 2025-10-17T08:52:28 >>> owfs 3.2p4 Installing to staging directory
> 2025-10-17T08:52:29 >>> owfs 3.2p4 Fixing libtool fDone in 7min 37s
> iles
> 2025-10-17T08:52:30 >>> owfs 3.2p4 Installing to target
> 2025-10-17T08:52:38 >>> python-pydantic-core 2.33.2 Installing to target
> 2025-10-17T08:52:52 >>> e2fsprogs 1.47.2 Building
> [...]
>
> Adding the --unbuffered argument to the final sed call, fixes that.
Hi Marcus,
Thank you for the extensive testing!
What you described is a valid reason I think to add the --unbuffered argument to
sed; I will respin a v2.
Best regards,
Vincent.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-10-17 14:40 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é
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é [this message]
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=aPJVOlZTJvdk65L8@debian \
--to=vincent.stehle@arm.com \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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