From: "WXbet" <WXbet@proton.me>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] knotty: show elapsed time on the task progress bar
Date: Wed, 26 Aug 2026 08:15:56 -0700 [thread overview]
Message-ID: <2789044.1787757356219607465@lists.openembedded.org> (raw)
In-Reply-To: <DB5PR02MB1021395256F54ECB1AC5FF3CBEFAE2@DB5PR02MB10213.eurprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
On Wed, Aug 26, 2026 at 04:41 PM, Peter Kjellerstedt wrote:
>
> On the other hand, the progress bars that are shown during the initial
> phase before the build tasks starts all use Progressbar's own Timer
> widget. I think it makes more sense to just use progressbar.Timer()
> rather than BBTimer().
The formatting is deliberate. The running-task lines right below the bar print their time through TerminalFilter.elapsed() , e.g. 16m34s. With progressbar.Timer the bar reads 0:16:34 , so the same screen would show two different time formats. The parsing-phase bars are gone by the time the task bar appears, so they never compete with it.
Timer.format_time is a staticmethod and Timer defines __slots__ , so it cannot be replaced per instance, hence the small subclass.
If you prefer consistency with progressbar's own format, this one-liner does it instead and I am happy to send it as v2:
- widgets = [' ', progressbar.Percentage(), ' ', progressbar.Bar()]
+ widgets = [' ', progressbar.Percentage(), ' ', progressbar.Bar(), ' ', progressbar.Timer(format='Elapsed: %s')]
[-- Attachment #2: Type: text/html, Size: 1423 bytes --]
next prev parent reply other threads:[~2026-08-26 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 19:39 [PATCH] knotty: show elapsed time on the task progress bar WXbet
2026-08-18 19:54 ` WXbet
2026-08-19 8:22 ` [bitbake-devel] " Alexander Kanavin
2026-08-19 9:33 ` WXbet
2026-08-26 13:03 ` WXbet
2026-08-26 14:41 ` [bitbake-devel] " Peter Kjellerstedt
2026-08-26 15:15 ` WXbet [this message]
2026-08-27 8:22 ` Peter Kjellerstedt
2026-08-27 10:43 ` WXbet
2026-08-27 10:01 ` [PATCH v2] " WXbet
2026-09-05 19:14 ` WXbet
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=2789044.1787757356219607465@lists.openembedded.org \
--to=wxbet@proton.me \
--cc=bitbake-devel@lists.openembedded.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