From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Uladzimir Bely <ubely@ilbers.de>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: sbuild race with sporadic build breakages
Date: Mon, 9 Sep 2024 13:53:36 +0300 [thread overview]
Message-ID: <79d3faf8-a35f-4fd0-ada2-8f8f69cdee8d@ilbers.de> (raw)
In-Reply-To: <187215a1-ff1b-48b4-979f-9b49689a78e7@siemens.com>
23/05/2024 20:08, 'Jan Kiszka' via isar-users wrote:
> 2024-05-23 15:16:22 - INFO - | E: /etc/schroot/chroot.d/isar-builder-3cef593b-e753-4463-a544-cea3d14532e2-41541: Failed to stat file: No such file or directory
Hello Jan,
I've finally found the root cause of this issue and it turns out that
schroot
is not fully thread safe when managing config files. Luckly this issue looks
quite easy to fix with one additional lock file, I've reported this
findings to
the upstream:
https://codeberg.org/shelter/reschroot/issues/10
--
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 on the web visit https://groups.google.com/d/msgid/isar-users/79d3faf8-a35f-4fd0-ada2-8f8f69cdee8d%40ilbers.de.
next prev parent reply other threads:[~2024-09-09 10:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 17:08 Jan Kiszka
2024-05-24 7:26 ` MOESSBAUER, Felix
2024-05-24 8:08 ` Anton Mikanovich
2024-05-24 8:52 ` Jan Kiszka
2024-05-24 9:30 ` Anton Mikanovich
2024-05-24 10:42 ` Jan Kiszka
2024-05-24 11:55 ` Anton Mikanovich
2024-06-17 7:44 ` Jan Kiszka
2024-06-17 8:32 ` Baurzhan Ismagulov
2024-06-17 12:55 ` Jan Kiszka
2024-06-17 14:12 ` Anton Mikanovich
2024-06-17 14:50 ` Jan Kiszka
2024-06-24 8:00 ` Uladzimir Bely
2024-06-24 9:13 ` Jan Kiszka
2024-09-09 10:53 ` Anton Mikanovich [this message]
2024-10-01 7:35 ` 'Jan Kiszka' via isar-users
2024-11-11 9:31 ` 'Jan Kiszka' via isar-users
2024-11-11 10:44 ` Anton Mikanovich
2024-11-11 12:04 ` 'Jan Kiszka' via isar-users
2024-11-11 14:28 ` 'Jan Kiszka' via isar-users
2024-11-11 14:37 ` Anton Mikanovich
2024-11-11 14:52 ` 'Jan Kiszka' via isar-users
2024-11-11 15:17 ` Anton Mikanovich
2024-11-11 15:56 ` 'Jan Kiszka' via isar-users
2024-11-11 17:58 ` 'MOESSBAUER, Felix' via isar-users
2024-11-11 19:48 ` 'Jan Kiszka' via isar-users
2024-11-13 6:51 ` 'MOESSBAUER, Felix' via isar-users
2024-11-13 7:00 ` 'Jan Kiszka' via isar-users
2024-12-05 15:57 ` Anton Mikanovich
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=79d3faf8-a35f-4fd0-ada2-8f8f69cdee8d@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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