From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: ubuntu-jammy: potential deadlock in do_deploy_deb
Date: Mon, 1 Jul 2024 13:02:54 +0000 [thread overview]
Message-ID: <befd05f63a411f63d60fa66131d1b107bdfe6119.camel@siemens.com> (raw)
In-Reply-To: <84190bb1d2acca1cec65a70e1177fd2e7229007a.camel@siemens.com>
On Mon, 2024-06-17 at 07:48 +0000, 'MOESSBAUER, Felix' via isar-users
wrote:
> Hi,
>
> I have a build for ubuntu-jammy, where the do_deploy_deb sometimes
> (>50% of the time) deadlocks (i.e. it never completes). I'm wondering
> if this is a generic issue, which just shows up in this
> configuration,
> or if it is really ubuntu only. On debian-bullseye and debian-
> bookworm
> builds I cannot reproduce this.
After some more digging I finally found the root-cause: Ubuntu uses
zstd as compression format for the .deb packages and there is a race
condition in the tool in combination with unzstd which makes the
reprepro includedeb hang (deadlock). This is also reported in [1].
The fix is already in debian sid, but there is neither a backports, nor
a stable update available. We also cannot easily backport by ourselves
as this is a host tool which is not run in a changeroot.
This more or less renders our Ubuntu support useless, as there is no
suitable host distribution that reliably is able to build these
targets.
Anyways, I'll try to request a stable update for debian and once
merged, propose a kas container update. Long story...
Felix
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056380
>
> ISAR revision: f7c0df35ae4ed44c741c98d9c003355e13e40e94
>
> The affected package is a rebuild of the upstream evolution package.
> The log of the do_deploy_deb step looks like this:
>
> deadlock:
> DEBUG: Executing shell function do_deploy_deb
> Not removed as not found: evolution-plugin-spamassassin
> Exporting indices...
> Not removed as not found: evolution-plugins
> Exporting indices...
> Not removed as not found: evolution-plugin-pstimport
> Exporting indices...
> Not removed as not found: evolution-common
> Exporting indices...
> Not removed as not found: evolution
> Exporting indices...
>
> successful operation:
> DEBUG: Executing shell function do_deploy_deb
> Not removed as not found: evolution-plugin-spamassassin
> Exporting indices...
> Not removed as not found: evolution-plugins
> Exporting indices...
> Not removed as not found: evolution-plugin-pstimport
> Exporting indices...
> Not removed as not found: evolution-common
> Exporting indices...
> Not removed as not found: evolution
> Exporting indices...
> Not removed as not found: evolution-plugins-experimental
> Exporting indices...
> Not removed as not found: evolution-plugin-bogofilter
> Exporting indices...
> Not removed as not found: libevolution
> Exporting indices...
> Not removed as not found: evolution-dev
> Exporting indices...
> Exporting indices...
> DEBUG: Shell function do_deploy_deb finished
>
> Best regards,
> Felix
>
> --
> Siemens AG, Technology
> Linux Expert Center
>
>
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2024-07-01 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 7:48 MOESSBAUER, Felix
2024-07-01 13:02 ` MOESSBAUER, Felix [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=befd05f63a411f63d60fa66131d1b107bdfe6119.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--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