From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 0/5] Rebuild mount logic
Date: Tue, 8 Jun 2021 10:54:00 +0200 [thread overview]
Message-ID: <20210608105400.685320b0@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <ae96adda-59a7-2f56-aa5a-a396eab48006@ilbers.de>
Am Tue, 8 Jun 2021 11:15:26 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> 08.06.2021 10:58, Henning Schild wrote:
> > This series makes things not build in containers anymore, which we
> > heavily rely on for CI. Exceptions in the mount logic.
> >
> > I would suggest to revert and investigate.
> >
> > Henning
>
> There is no any build issues with container targets at
> ci.isar-build.org. Do you have any logs?
I think the core of the problem is that "umount" can fail and that
failure is not handled. Before we maybe ignored it ...
In the logs i sent it failed with "target is busy"
Henning
next prev parent reply other threads:[~2021-06-08 8:58 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 [this message]
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
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=20210608105400.685320b0@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@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