Re: sbuild race with sporadic build breakages

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 01.10.24 09:35, Jan Kiszka wrote:
> On 09.09.24 12:53, Anton Mikanovich wrote:
>> 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
>>
> 
> Is there a way to mitigate this outside of sbuild? Upstream shows no
> reactions so far (already pinged them again?), and then it will still
> take a while to get that via stable debian updates and finally the kas
> container.
> 

Ping: Would locking outside of schroot mean that isar had to serialize
all build jobs? Or why don't we have workaround yet?

BTW, you should also create a Debian bug for this. Seems there is none
yet, right?

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/fde642d8-30d0-44b1-ad64-20fbc3ccfa71%40siemens.com.