ci failure of mc:container-amd64-buster

[Jan Kiszka]

Hi all,

will this be addressed by the pending container patches? Or is it mount-
changes related?

NOTE: recipe hello-isar-0.3-a18c14c-r0: task do_dpkg_build: Failed
ERROR: mc:container-amd64-buster:hello-isar-0.3-a18c14c-r0 do_dpkg_build: Error executing a python function in exec_python_func() autogenerated:
The stack trace of python calls that resulted in this exception/failure was:

[cut out useless python dump - should eventually be disabled again...]

Exception: bb.process.ExecutionError: Execution of '/builds/BLKE9aZ_/0/ebsy/debian/isar/build/tmp/work/debian-buster-amd64/hello-isar/0.3-a18c14c-r0/temp/run.buildchroot_undo_mounts.56304' failed with exit code 32:
umount: /builds/BLKE9aZ_/0/ebsy/debian/isar/build/tmp/work/debian-buster-amd64/buildchroot-target/1.0-r0/rootfs/sys/fs/cgroup: target is busy.
WARNING: exit code 32 from a shell command.
ERROR: Logfile of failure stored in: /builds/BLKE9aZ_/0/ebsy/debian/isar/build/tmp/work/debian-buster-amd64/hello-isar/0.3-a18c14c-r0/temp/log.do_dpkg_build.56304
ERROR: Task (mc:container-amd64-buster:/builds/BLKE9aZ_/0/ebsy/debian/isar/meta-isar/recipes-app/hello-isar/hello-isar.bb:do_dpkg_build) failed with exit code '1'

Jan

--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

[Henning Schild]

Very likely mount-related. Also seeing such weird things in another
layer. The upcoming container changes only deal with the two values in
a tag becoming less static.

What you see here seems like a build problem that comes way before the
imager ... and what could hit you with wic, ext4 ... or whatever.

Henning

Am Wed, 11 Aug 2021 17:22:31 +0200
schrieb Jan Kiszka <jan.k...@siemens.com>: