Re: [PATCH v4 0/5] expand-on-first-boot btrfs and CI testing

[Henning Schild <henning.schild@siemens.com>]

Hi all,

i decided to merge the re-introduction of btrfs with the CI series i
had going on. Because that is all so important yet seemingly fragile
that we really do not want any big change without CI.

this is based on
"expand-on-first-boot: switch back away from systemd-growfs"
which should be merged because it breaks several machines like rpis,
with the udev race we found lately

It is tested manually in qemu, especially debian-bullseye (btrfs
candidate) and on that formerly affected rpi.
In addition i pushed it here to trigger CI runs at ilbers already:
https://github.com/henning-schild-work/isar/tree/henning/ilbers-ci

I get the feeling we really need a way to log in to the images running
in CI and run test code there. Only waiting for the login prompt and
hoping for bits in the kernel log is not powerful enough do perform
real tests. That is something to improve at some point.

regards,
Henning

Am Tue, 13 Dec 2022 11:15:04 +0100
schrieb henning.schild@siemens.com:

> From: Henning Schild <henning.schild@siemens.com>
> 
> changes since v3:
>  - rebased on "expand-on-first-boot: switch back away from
> systemd-growfs"
>  - implement btrfs resizing and CI testing it
>  - put the padding wks entry into an include
> 
> changes since v2:
>  - add python namespace prefix for the bitbake get functions
>  - install only in images that use WKS_FILEs that have the "gap"
> 
> changes since v1:
>  - complete rewrite to not focus only on the tests but rather the
>    feature for all examples
> 
> This first was only about testing but meanwhile has a focus on
> enabling the expand feature in all example images anyhow, and later
> look for traces of that happening in CI test where we can.
> We install the application in any image and in the wic images add some
> scratch space at the end. That will enable improved interactive use of
> all those wic images, so makes sense apart from any testing.
> Later use the log reading feature of the qemu tests to look for traces
> of successful resizing for non ubuntu images. In ubuntu the
> console_loglevel is not verbose enough to find traces.
> 
> 
> Henning Schild (5):
>   expand-on-first-boot: support resizing a btrfs
>   meta-isar: introduce an example to use btrfs
>   CI: improve cibuilder readability
>   meta-isar: install expand-on-first-boot in most images and add space
>   CI: expect a message about filesystem resize vom expand script
> 
>  meta-isar/conf/machine/qemuamd64.conf         |  6 ++++
>  meta-isar/conf/machine/virtualbox.conf        |  1 +
>  meta-isar/conf/machine/vmware.conf            |  1 +
>  .../conf/multiconfig/qemuarm-bookworm.conf    |  1 +
>  .../lib/wic/canned-wks/expand-padding.wks.inc |  5 +++
>  .../lib/wic/canned-wks/sdimage-efi-btrfs.wks  | 11 ++++++
>  .../lib/wic/canned-wks/sdimage-efi-sd.wks     |  2 ++
>  .../lib/wic/canned-wks/sdimage-efi.wks        |  2 ++
>  .../files/expand-last-partition.sh            | 35
> ++++++++++++++++--- testsuite/cibuilder.py                        |
> 28 ++++++++++++--- 10 files changed, 83 insertions(+), 9 deletions(-)
>  create mode 100644
> meta-isar/scripts/lib/wic/canned-wks/expand-padding.wks.inc create
> mode 100644 meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-btrfs.wks
>