On Sun, 12 Feb 2017, Ghislain Vaillant wrote: > On Sun, 2017-02-12 at 11:35 +0100, Santiago Vila wrote: > > On Sat, Feb 11, 2017 at 03:27:33PM +0000, Ghislain Vaillant wrote: > > > Hi Santiago, thanks for reporting this issue, > > > > > > > The bug should be reproducible with sbuild on a single CPU virtual > > > > machine, > > > > provided you try enough times (as the failure happens randomly). > > > > > > Could you apply the same tests to src:python-qtawesome and report > > > whether you get the same outcome (i.e. random success / failure). > > > > I built python-qtawesome 100 times and it failed none. > > That's interesting. So, a fix was required for builds on Ubuntu, but > not on Debian.
Or maybe it just does not happen in a single-CPU machine, or it does not happen when the kernel is the kernel from stretch, or something alike. > > However, there is another package involving xvfb-run which always fail > > for me. Can you reproduce this bug? > > > > https://bugs.debian.org/848063 > > > > The maintainer downgraded it to important, but it fails for me 100% of > > the time, so it's not really very random (for me at least). > > I built it successfully with sbuild on my local machine. I also did a > successful trial run on debomatic: > > http://debomatic-i386.debian.net/distribution#unstable/ri-li/2.0.1+ds-4/buildlog > > I understand Markus' frustration considering the package used to build > fine before, still builds ok now (works on my sbuild and on dom) but > fails with your setup, with no obvious clue as where the failure could > originate from. Well, I hope you can understand my frustration too: ri-li fails for me 97% of the time (which is almost always), on different machines, and it seems to fail always as well in the reproducible builds autobuilders. In such conditions the least I would expect from Markus is to accept the offer I made (i.e. free access to a machine where this happens always). Thanks.