From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
"Cirujano-Cuesta, Silvano" <silvano.cirujano-cuesta@siemens.com>
Subject: Re: ci failure of mc:container-amd64-buster
Date: Wed, 11 Aug 2021 19:10:16 +0200 [thread overview]
Message-ID: <20210811191016.37297a1c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <87cef6ee-411c-b611-4fb4-3957573d9455@siemens.com>
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.kiszka@siemens.com>:
> 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
>
prev parent reply other threads:[~2021-08-11 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 15:22 Jan Kiszka
2021-08-11 17:10 ` Henning Schild [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=20210811191016.37297a1c@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=silvano.cirujano-cuesta@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