public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/4] Fix various race conditions on multiconfig
Date: Thu, 10 Sep 2026 16:01:57 +0200	[thread overview]
Message-ID: <20260910140201.250854-1-felix.moessbauer@siemens.com> (raw)

When running under multiconfig, various race conditions can occur due
to simultaneous access to the isar-apt. We fix these by ensuring
that the deployment of the source archive and the .debs is idempotent.

While investigating this, we noticed that the existing deb_clean no
longer removes the artifacts from the apt-cache, as it reads the "what
to clean" from a dir that is previously removed by the internal
clean logic of the sstate. This bug is fixed as well (p2).

Note, that the root cause of the races has been found by an LLM,
which had access to the build log of a failed execution.

Best regards,
Felix Moessbauer
Siemens AG

Felix Moessbauer (4):
  fix(dpkg-build): make sstate updates of DEPLOY_DIR_DEB atomic
  fix(dpkg-build): clean isar-apt by source package and arch
  fix(dpkg-build): scan DEPLOY_DIR_DEB only once in do_deploy_deb
  fix(dpkg-source): make sstate updates of DEPLOY_DIR_SRC atomic

 meta/classes-recipe/dpkg-base.bbclass   | 53 +++++++++++++++++++------
 meta/classes-recipe/dpkg-source.bbclass | 35 ++++++++++++----
 meta/classes-recipe/repository.bbclass  | 22 ++++++++++
 3 files changed, 89 insertions(+), 21 deletions(-)

-- 
2.55.0

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20260910140201.250854-1-felix.moessbauer%40siemens.com.

             reply	other threads:[~2026-09-10 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 14:01 'Felix Moessbauer' via isar-users [this message]
2026-09-10 14:01 ` [PATCH 1/4] fix(dpkg-build): make sstate updates of DEPLOY_DIR_DEB atomic 'Felix Moessbauer' via isar-users
2026-09-10 14:01 ` [PATCH 2/4] fix(dpkg-build): clean isar-apt by source package and arch 'Felix Moessbauer' via isar-users
2026-09-10 14:02 ` [PATCH 3/4] fix(dpkg-build): scan DEPLOY_DIR_DEB only once in do_deploy_deb 'Felix Moessbauer' via isar-users
2026-09-10 14:02 ` [PATCH 4/4] fix(dpkg-source): make sstate updates of DEPLOY_DIR_SRC atomic 'Felix Moessbauer' via isar-users
2026-09-15  8:31 ` [PATCH 0/4] Fix various race conditions on multiconfig Zhihang Wei

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=20260910140201.250854-1-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.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