From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Cc: "IPFire: Tremer, Michael" <michael.tremer@ipfire.org>
Subject: How to disable the item timer? (was: Re: Unending item build)
Date: Mon, 15 Jun 2026 14:22:17 +0200 [thread overview]
Message-ID: <d17947b6-cc6f-4691-9927-26cef1ef6bd2@ipfire.org> (raw)
In-Reply-To: <598D4CBF-4F7F-401C-9B59-EF6298758777@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
Hi Michael,
On 09.06.2026 20:24, Michael Tremer wrote:
> You can run the build like this: ./make.sh build < /dev/null
>
> The script will then think that it is not talking to a console and just print the default output instead of the timer.
This worked for a while - today the system suddenly thinks that it needs
*two* timers - on 'next'. Hm!
One timer is always "0", the other is showing the build time of the
current item. Both are not counting (see screenshot). Besides that, all
is running, but... ;-)
Is there a chance to disable these timers completely? The only one which
I think is useful would be the buildtime of the whole build at the end.
I don't need nothing more...
Best
Matthias
[-- Attachment #2: 2026-06-15 - Timers on Devel 2.jpg --]
[-- Type: image/jpeg, Size: 69699 bytes --]
next prev parent reply other threads:[~2026-06-15 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 11:58 Unending item build Matthias Fischer
2026-06-08 14:03 ` Michael Tremer
2026-06-08 14:09 ` Matthias Fischer
2026-06-08 16:14 ` Adolf Belka
2026-06-08 16:55 ` Stefan Schantl
2026-06-09 17:47 ` Matthias Fischer
2026-06-09 18:24 ` Michael Tremer
2026-06-15 12:22 ` Matthias Fischer [this message]
2026-06-16 10:58 ` How to disable the item timer? (was: Re: Unending item build) Michael Tremer
2026-06-16 12:02 ` How to disable the item timer? Matthias Fischer
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=d17947b6-cc6f-4691-9927-26cef1ef6bd2@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@ipfire.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