Le sam. 5 avr. 2025 à 18:06, Santiago Vila <sanv...@debian.org> a écrit :
> reopen 1078886 > thanks > > Hello. I'm really sorry to reopen this, but the recent change > did not fix the reported problem. > > I'm attaching my build history, where 1.0.5-5 is the version > in unstable and 1.0.5-4.1 was my internal version where I > tested the proposed patch (which I assume it would still work, > since the issue seems to be a concurrency problem) Weird, because I reproduce, and it got way better after the fix. I'll investigate further. > I'm putting a bunch of failed build logs here: > > https://people.debian.org/~sanvila/build-logs/202504/ > > (btw: only if it helps, I would be willing to join the team > and fix this myself, that would also allow me to > fix this in stable without bothering you. I have joined > other teams for QA purposes in the past, and it seems to be > a form of collaboration which seems to work well). > Yes, you can, however since I already spent some time digging, I might as well continue to try to fix the test. If I fail to find out, I'll just disable them.
