From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/5] Rebuild mount logic
Date: Tue, 22 Jun 2021 17:40:23 +0300 [thread overview]
Message-ID: <94ad1d2f-ddfd-ebc3-8687-86dcef0a0b9a@ilbers.de> (raw)
In-Reply-To: <246fd202-0ec2-563b-90fe-3c4177fda44e@siemens.com>
21.06.2021 18:54, Jan Kiszka wrote:
> This one is still not stable (reverting my claim "current next builds
> fine"):
>
> NOTE: recipe buildchroot-target-1.0-r0: task do_rootfs_postprocess: Started
> ERROR: mc:rpi-stretch:buildchroot-target-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:
> File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
> 0001:
> *** 0002:do_rootfs_postprocess(d)
> 0003:
> File: '/builds/Vs1BETDQ/0/ebsy/debian/isar/meta/classes/rootfs.bbclass', lineno: 298, function: do_rootfs_postprocess
> 0294: for i, cmd in enumerate(cmds):
> 0295: bb.build.exec_func(cmd, d)
> 0296: progress_reporter.update(int(i / len(cmds) * 100))
> 0297:
> *** 0298: bb.build.exec_func('rootfs_undo_mounts', d)
> 0299:}
> 0300:addtask rootfs_postprocess before do_rootfs
> 0301:
> 0302:python do_rootfs() {
> File: '/builds/Vs1BETDQ/0/ebsy/debian/isar/bitbake/lib/bb/build.py', lineno: 251, function: exec_func
> 0247: with bb.utils.fileslocked(lockfiles):
> 0248: if ispython:
> 0249: exec_func_python(func, d, runfile, cwd=adir)
> 0250: else:
> *** 0251: exec_func_shell(func, d, runfile, cwd=adir)
> 0252:
> 0253: try:
> 0254: curcwd = os.getcwd()
> 0255: except:
> File: '/builds/Vs1BETDQ/0/ebsy/debian/isar/bitbake/lib/bb/build.py', lineno: 452, function: exec_func_shell
> 0448: with open(fifopath, 'r+b', buffering=0) as fifo:
> 0449: try:
> 0450: bb.debug(2, "Executing shell function %s" % func)
> 0451: with open(os.devnull, 'r+') as stdin, logfile:
> *** 0452: bb.process.run(cmd, shell=False, stdin=stdin, log=logfile, extrafiles=[(fifo,readfifo)])
> 0453: finally:
> 0454: os.unlink(fifopath)
> 0455:
> 0456: bb.debug(2, "Shell function %s finished" % func)
> File: '/builds/Vs1BETDQ/0/ebsy/debian/isar/bitbake/lib/bb/process.py', lineno: 182, function: run
> 0178: if not stderr is None:
> 0179: stderr = stderr.decode("utf-8")
> 0180:
> 0181: if pipe.returncode != 0:
> *** 0182: raise ExecutionError(cmd, pipe.returncode, stdout, stderr)
> 0183: return stdout, stderr
> Exception: bb.process.ExecutionError: Execution of '/builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/temp/run.rootfs_undo_mounts.19080' failed with exit code 32:
> umount: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/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/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/temp/log.do_rootfs_postprocess.19080
> NOTE: recipe buildchroot-target-1.0-r0: task do_rootfs_postprocess: Failed
> ERROR: Task (mc:rpi-stretch:/builds/Vs1BETDQ/0/ebsy/debian/isar/meta/recipes-dev
Looks like a race.
It was not a problem when we left mounts till the end of the build.
I will try to look for any possible reasons.
> And then also
>
> NOTE: Tasks Summary: Attempted 1181 tasks of which 214 didn't need to be rerun and 1 failed.
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/dev left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/dev/pts left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/dev/mqueue left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/dev/termination-log left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/dev/shm left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/proc left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/sys left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/sys/fs/cgroup left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/sys/fs/cgroup/cpuset left mounted, unmounting...
> WARNING: /builds/Vs1BETDQ/0/ebsy/debian/isar/build/tmp/work/raspbian-stretch-armhf/buildchroot-target/1.0-r0/rootfs/downloads left mounted, unmounting...
>
> Summary: 1 task failed:
> mc:rpi-stretch:/builds/Vs1BETDQ/0/ebsy/debian/isar/meta/recipes-devtools/buildchroot/buildchroot-target.bb:do_rootfs_postprocess
>
>
> Though I suspect and hope the latter is related to the former.
Yes, it's just a 'visualization' of mount points cleanup at finalize
task, called just after the build was failed.
It supposed to be empty for successful builds, but not for failed ones.
> Retrying, to see if we have a race (likely) or something stable.
>
> Jan
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2021-06-22 14:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 6:25 Anton Mikanovich
2021-05-08 6:25 ` [PATCH v3 1/5] dpkg: Make mount buildroot reliable Anton Mikanovich
2021-06-08 8:09 ` Henning Schild
2021-06-08 8:31 ` Anton Mikanovich
2021-06-08 8:49 ` Henning Schild
2021-07-01 11:55 ` Jan Kiszka
2021-05-08 6:25 ` [PATCH v3 2/5] buildchroot: Unmount buildchroot mounts if not needed Anton Mikanovich
2021-05-08 6:25 ` [PATCH v3 3/5] rootfs: Unmount rootfs " Anton Mikanovich
2021-05-08 6:25 ` [PATCH v3 4/5] wic: Unmount dirs after usage Anton Mikanovich
2021-05-08 6:25 ` [PATCH v3 5/5] events: Warn if mounted paths left Anton Mikanovich
2021-07-01 11:51 ` Jan Kiszka
2021-06-08 7:58 ` [PATCH v3 0/5] Rebuild mount logic Henning Schild
2021-06-08 8:15 ` Anton Mikanovich
2021-06-08 8:42 ` Henning Schild
2021-06-08 8:54 ` Henning Schild
2021-06-10 7:12 ` Anton Mikanovich
2021-06-10 15:02 ` Henning Schild
2021-06-21 15:54 ` Jan Kiszka
2021-06-22 14:40 ` Anton Mikanovich [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=94ad1d2f-ddfd-ebc3-8687-86dcef0a0b9a@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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