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