From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v6 0/6] Restore downstream mounts compatibility
Date: Mon, 13 Sep 2021 18:03:07 +0300 [thread overview]
Message-ID: <46699d00-aa70-0ce5-c120-fe87efcab873@ilbers.de> (raw)
In-Reply-To: <20210909111715.3c7e5da3@md1za8fc.ad001.siemens.net>
09.09.2021 12:17, Henning Schild wrote:
>
> I just wrote an email on that. Some builds are getting stuck and it
> seems that ROOTFS/isar.lock is part of the problem. The layer does have
> a few recipes that use buildchroot_do_mounts but nothing with locking.
> Investigation is ongoing, but if you know the problem that builds get
> stuck at do_deploy_deb that would be interesting to us.
According to that email isar/isar.lock file is the one which was stuck,
but not ROOTFS/isar.lock.
So this is not a lockfile used for mounts control.
I've analyzed 3 different stuck builds (54664183, 54679509 and 54679508)
and see that all three are supposed to stuck on different tasks
(do_dpkg_build, do_install_builddeps and do_apt_fetch) of three
different recipes (can share the lists of those recipes if needed).
There were no CI artifacts saved, so it is hard to say what's going on
inside.
Suggest looking into appropriate logfile when this happens again until
the build fail by timeout.
--
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-09-13 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 10:23 Anton Mikanovich
2021-08-23 10:23 ` [PATCH v6 1/6] Revert "dpkg: Make mount buildroot reliable" Anton Mikanovich
2021-08-23 10:23 ` [PATCH v6 2/6] dpkg: Limit unmount loop Anton Mikanovich
2021-08-23 10:23 ` [PATCH v6 3/6] dpkg-base: Clean up unmounting in do_dpkg_build() Anton Mikanovich
2021-08-23 10:23 ` [PATCH v6 4/6] events: Do not warn on left mounts by default Anton Mikanovich
2021-08-23 10:23 ` [PATCH v6 5/6] Revert "rootfs: Unmount rootfs mounts if not needed" Anton Mikanovich
2021-08-23 10:23 ` [PATCH v6 6/6] Revert "buildchroot: Unmount buildchroot " Anton Mikanovich
2021-08-27 17:16 ` [PATCH v6 0/6] Restore downstream mounts compatibility Anton Mikanovich
2021-08-30 8:25 ` Jan Kiszka
2021-08-30 18:46 ` Anton Mikanovich
2021-09-08 15:48 ` Henning Schild
2021-09-09 8:13 ` Anton Mikanovich
2021-09-09 9:17 ` Henning Schild
2021-09-13 15:03 ` 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=46699d00-aa70-0ce5-c120-fe87efcab873@ilbers.de \
--to=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--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