public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: quirin.gylstorff@siemens.com, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2 1/1] generate_initramfs: fix progress reporting on dracut
Date: Wed, 26 Nov 2025 10:43:40 +0100	[thread overview]
Message-ID: <30f2c7e9-5cf3-47d7-a6dd-a605cc009a1b@ilbers.de> (raw)
In-Reply-To: <20251117115104.410537-1-felix.moessbauer@siemens.com>

Applied to next, thanks.

On 11/17/25 12:51, 'Felix Moessbauer' via isar-users wrote:
> When generating the initrd with dracut, the copy-in operations emit
> output that is different from the initramfs-tools output. This patch
> extends the progress parser to also support the dracut output.
>
> Prior to the patch, the progress bar stayed at 0% until the task was
> finished.
>
> Reported-by: Jan Kiszka <jan.kiszka@siemens.com>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> Changes since v1:
> - format code according to black formatter rules
>
>   meta/lib/rootfs_progress.py | 6 +++++-
>   1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/meta/lib/rootfs_progress.py b/meta/lib/rootfs_progress.py
> index 1cc70c87..0ac81e14 100644
> --- a/meta/lib/rootfs_progress.py
> +++ b/meta/lib/rootfs_progress.py
> @@ -81,7 +81,11 @@ class InitrdProgressHandler(PkgsProgressHandler):
>               self._stage = 'post-prepare'
>   
>       def process_line(self, line):
> -        if line.startswith('Adding module'):
> +        if (
> +            line.startswith("Adding module")
> +            or line.startswith("dracut-install: cp")
> +            or line.startswith("dracut-install: Failed to find module")
> +        ):
>               self._pkg += 1
>           elif line.startswith('(excluding'):
>               self._pkg += len(line.split(' ')) - 1

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/30f2c7e9-5cf3-47d7-a6dd-a605cc009a1b%40ilbers.de.

      reply	other threads:[~2025-11-26  9:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 11:51 'Felix Moessbauer' via isar-users
2025-11-26  9:43 ` Zhihang Wei [this message]

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=30f2c7e9-5cf3-47d7-a6dd-a605cc009a1b@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@siemens.com \
    /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