From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
isar-users@googlegroups.com, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v2 3/5] rootfs: Unmount rootfs mounts if not needed
Date: Thu, 12 Aug 2021 11:25:49 +0200 [thread overview]
Message-ID: <637cb0c9-750f-b95e-e216-4d8daf957d55@siemens.com> (raw)
In-Reply-To: <e3f40d69-fcb3-2fa7-97f3-28661c870914@ilbers.de>
On 12.08.21 11:09, Anton Mikanovich wrote:
> 12.08.2021 08:39, Jan Kiszka wrote:
>> This is simply from running next in CI:
>>
>> ERROR: mc:de0-nano-soc-buster:buildchroot-host-1.0-r0
>> do_rootfs_postprocess: Error executing a python function in
>> exec_python_func() autogenerated:
>> The stack trace of python calls that resulted in this
>> exception/failure was:
>>
>> [cut useless backtrace]
>>
>> buster-armhf/buildchroot-host/1.0-r0/temp/run.rootfs_undo_mounts.65491' failed
>> with exit code 32:
>> umount:
>> /builds/BLKE9aZ_/0/ebsy/debian/isar/build/tmp/work/debian-buster-armhf/buildchroot-host/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-armhf/buildchroot-host/1.0-r0/temp/log.do_rootfs_postprocess.65491
>>
>> NOTE: recipe buildchroot-host-1.0-r0: task do_rootfs_postprocess: Failed
>> ERROR: Task
>> (mc:de0-nano-soc-buster:/builds/BLKE9aZ_/0/ebsy/debian/isar/meta/recipes-devtools/buildchroot/buildchroot-host.bb:do_rootfs_postprocess)
>> failed with exit code '1'
>>
>> It's analogous to
>> https://groups.google.com/d/msgid/isar-users/87cef6ee-411c-b611-4fb4-3957573d9455%40siemens.com,
>> just clearly pointing to this series.
>
> Does this and
> https://groups.google.com/d/msgid/isar-users/87cef6ee-411c-b611-4fb4-3957573d9455%40siemens.com
> have happened on CI inside docker? Let me look into this issue anyway.
>
Yes, in gitlab-ci. That's how we are testing because that's Isar is
generally used.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-08-12 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 14:58 [PATCH v2 0/5] isar: Rebuild mount logic Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 1/5] dpkg: Make mount buildroot reliable Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 2/5] buildchroot: Unmount buildchroot if not needed Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 3/5] rootfs: Unmount rootfs mounts " Anton Mikanovich
2021-08-12 5:39 ` Jan Kiszka
2021-08-12 9:09 ` Anton Mikanovich
2021-08-12 9:25 ` Jan Kiszka [this message]
2021-08-13 16:27 ` Anton Mikanovich
2021-08-15 19:05 ` Jan Kiszka
2021-04-21 14:58 ` [PATCH v2 4/5] wic: Unmount dirs after usage Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 5/5] events: Warn if mounted paths left 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=637cb0c9-750f-b95e-e216-4d8daf957d55@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amikan@ilbers.de \
--cc=ibr@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