From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: potential race condition in sbuild post commands
Date: Wed, 17 Jan 2024 15:00:05 +0000 [thread overview]
Message-ID: <9bdf88ba27c9b12594bb490640ce97810566cf62.camel@siemens.com> (raw)
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
--
Siemens AG, Technology
Linux Expert Center
next reply other threads:[~2024-01-17 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 15:00 MOESSBAUER, Felix [this message]
2024-01-18 8:32 ` Anton Mikanovich
2024-01-18 9:17 ` MOESSBAUER, Felix
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=9bdf88ba27c9b12594bb490640ce97810566cf62.camel@siemens.com \
--to=felix.moessbauer@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