public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: potential race condition in sbuild post commands
Date: Thu, 18 Jan 2024 09:17:43 +0000	[thread overview]
Message-ID: <0b00e444ae3bf54ade0008c6edc11b6b065a188c.camel@siemens.com> (raw)
In-Reply-To: <f7a26994-469d-4a0e-8e46-0dbb74f2e3ca@ilbers.de>

On Thu, 2024-01-18 at 10:32 +0200, Anton Mikanovich wrote:
> 17/01/2024 17:00, 'MOESSBAUER, Felix' via isar-users wrote:
> > Dear devs,
> > 
> > I recently got the following error in multiple layers
> > (do_dpkg_build):
> > 
> > cp: cannot stat '/var/cache/apt/archives/*.deb': No such file or
> > directory
> > > 
> > > E: Command '[ -z "$(find /var/cache/apt/archives -maxdepth 1 -
> > > name
> > '*.deb' -print -quit)" ] || cp -Ln --no-preserve=owner
> > /var/cache/apt/archives/*.deb -t /home/builder/gasket-module-rt-
> > amd64/rootfs/var/cache/apt/archives/' failed to run.
> > > 
> > > Finished processing commands.
> > 
> > It looks like the copy operation has some race with a cleanup
> > operation. Is this already a known issue? I did not yet start
> > bisecting
> > or investigating this.
> > 
> > ISAR version: 1c509852c5a724a2c3ba401108d95fb1bfa36f90
> > 
> > Best regards,
> > Felix
> > 
> Hello Felix,
> It looks like a new issue, we will try to reproduce it.
> Are there any preconditions that can helpfull?
> (DL_DIR path, is it empty on beginning, etc)

Hi, it looks like the patch 1c509852 makes this more likely to show up.
Also, a big machine with many cores helps to reproduce and running kas-
container clean from time to time (or delete the build/tmp dir) between
the builds.

On one of our internal layers, I ran into this issue almost 100% of the
time. By that I think it will be easy to reproduce.

Best regards,
Felix

> 

-- 
Siemens AG, Technology
Linux Expert Center



      reply	other threads:[~2024-01-18  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 15:00 MOESSBAUER, Felix
2024-01-18  8:32 ` Anton Mikanovich
2024-01-18  9:17   ` 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=0b00e444ae3bf54ade0008c6edc11b6b065a188c.camel@siemens.com \
    --to=felix.moessbauer@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