From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: isar-apt locking: install_imager_deps vs rootfs_install (was: Re: dpkg: error: cannot stat pathname '/tmp/apt-dpkg-install...)
Date: Wed, 18 Sep 2019 15:39:32 +0200 [thread overview]
Message-ID: <20190918133932.7gzax63qwnz6kpno@yssyq.m.ilbers.de> (raw)
In-Reply-To: <0f8729f3-68e0-f6af-b75f-b7729078a039@siemens.com>
On Mon, Sep 02, 2019 at 10:08:38AM +0200, Jan Kiszka wrote:
> Just had this two times in a row now, so I dug deeper: The failure was
> always around self-built u-boot-tools and two images pulling that in
> more or less in parallel to a third one generating that package once
> again. All are sharing the same u-boot version for custom builds, thus
> u-boot-tools gets deployed multiple times.
>
> Looking at our locking around isar-apt I noticed that we hold the lock
> for install_imager_deps, but we do not for rootfs_install. Why should
> both be different? I played with a shared isar-apt lock around
> rootfs_install, to avoid massive serialization, and that didn't make the
> issue show up again, so far. But does it make sense?
I think it does.
With kind regards,
Baurzhan.
prev parent reply other threads:[~2019-09-18 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 20:22 dpkg: error: cannot stat pathname '/tmp/apt-dpkg-install Jan Kiszka
2019-08-26 20:59 ` Baurzhan Ismagulov
[not found] ` <136f3300-8dc3-5f42-13fc-4c04414f7801@siemens.com>
2019-09-02 8:08 ` isar-apt locking: install_imager_deps vs rootfs_install (was: Re: dpkg: error: cannot stat pathname '/tmp/apt-dpkg-install...) Jan Kiszka
2019-09-18 13:39 ` Baurzhan Ismagulov [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=20190918133932.7gzax63qwnz6kpno@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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