From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Moessbauer,
Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
"amikan@ilbers.de" <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "ubely@ilbers.de" <ubely@ilbers.de>, "ibr@ilbers.de" <ibr@ilbers.de>
Subject: Re: sbuild race with sporadic build breakages
Date: Mon, 11 Nov 2024 20:48:31 +0100 [thread overview]
Message-ID: <5ff31565-d9c3-4791-9874-107eb24492cd@siemens.com> (raw)
In-Reply-To: <3ae3bf411ce45c92fbad61e674bc6af08c8b0c2f.camel@siemens.com>
On 11.11.24 18:58, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
> On Mon, 2024-11-11 at 16:56 +0100, Jan Kiszka wrote:
>> On 11.11.24 16:17, Anton Mikanovich wrote:
>>> 11/11/2024 16:52, Jan Kiszka wrote:
>>>> We could only lock known sessions against each other. But that
>>>> would
>>>> already help everything that runs in a CI runner, maybe in a kas-
>>>> isar
>>>> container. Not perfect but would probably address 99% of cases
>>>> today.
>>>>
>>>> Jan
>>>>
>>> This will result in serialization of do_dpkg_build tasks and will
>>> cause
>>> Isar
>>> slowdown.
>>>
>>
>> OK, that was the information I was looking for - and was afraid of.
>>
>> But even if your PR would be merged tomorrow (which is completely
>> unpredictable right now), it would still require backports to
>> bookworm
>> at least, and those would need to be deployed locally or integrated
>> into
>> future versions of kas. All that is not going to happen soon - if at
>> all. It may even be that only trixes schroot will have all what we
>> need.
>
> We have similar problems with apt and proper rate-limit handling. But
> that's OT.
>
> At a second thought I'm wondering if we should drop schroot at all and
> use mmdebstrap + unshare. By that, the sbuild also does no longer
> require root access. I'm running sbuild with unshare backend for some
> time locally now (not with ISAR, though).
>
https://lists.debian.org/debian-devel/2024/06/msg00257.html - there is
likely no simple answer for the backend yet.
BTW, would unshare work at all inside our build containers?
Jan
--
Siemens AG, Technology
Linux Expert Center
--
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/5ff31565-d9c3-4791-9874-107eb24492cd%40siemens.com.
next prev parent reply other threads:[~2024-11-11 19:48 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
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 [this message]
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=5ff31565-d9c3-4791-9874-107eb24492cd@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--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