From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v3 3/3] CI: expect a message about filesystem resize vom expand script
Date: Fri, 18 Nov 2022 21:17:42 +0100 [thread overview]
Message-ID: <20221118211742.32fb921f@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <7c57f069-8d86-4dd8-6479-1ba45dfb8e91@ilbers.de>
Am Thu, 17 Nov 2022 21:44:37 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> 16.11.2022 17:36, Henning Schild wrote:
> > We have added the expand-on-first-boot recipe and some space to
> > grow to our example images. So now any image using wic should
> > "expand" on its first boot. And the kernel actually leaves a
> > message for us to read, at least on debian but not on ubuntu.
> >
> > Signed-off-by: Henning Schild <henning.schild@siemens.com>
>
> Hello Henning,
>
> It looks like wic usage check do not work (for example on
> qemuarm-bullseye). Did you test it on targets we have in CI?
>
My latest pipeline in your CI only pointed out an issue with a
container and a missing kernel, which seems to be an issue in "next"
anyhow.
I did some manual build tests to boot tests all ran on your infra.
Henning
next prev parent reply other threads:[~2022-11-18 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 14:36 [PATCH v3 0/3] expand-on-first-boot CI testing Henning Schild
2022-11-16 14:36 ` [PATCH v3 1/3] CI: improve cibuilder readability Henning Schild
2022-11-16 14:36 ` [PATCH v3 2/3] meta-isar: install expand-on-first-boot in most images and add space Henning Schild
2022-11-16 14:36 ` [PATCH v3 3/3] CI: expect a message about filesystem resize vom expand script Henning Schild
2022-11-17 18:44 ` Anton Mikanovich
2022-11-18 20:17 ` Henning Schild [this message]
2022-11-21 8:00 ` Anton Mikanovich
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=20221118211742.32fb921f@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.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