On Thu, 8 Sep 2016, gregor herrmann wrote: > Logs attached. Unfortunately I don't have any idea on how to fix the > problem, but if you want me to do something else just shout.
Well, if you don't mind burning a bunch of additional CPU cycles, I would continue to build it several times until it fails again. (If you tried three times and it failed once, it seems likely that it happens again). Then it would be interesting to see if the test which fails is the same it failed the first time, which, in your case, was this one: Failed tests: DatagramBindTest>AbstractBindTest.testUnbindDisconnectsClients:187 expected:<5> but was:<4> I have not analyzed my build logs, but I guess this is unfortunately not the same test which fails for me. BTW: I try to be objective by never reporting something when it only happens to me. This is why I sometimes say "here is a build log and it also fails in reproducible builds" or also "here you have several build logs from several different autobuilders". I think it would be just fair to ask the maintainer to be objective as well and consider whether it is really justified to downgrade the severity of a FTBFS bug when everybody else get a FTBFS too and his computer is the only one in which it may not be reproduced. If it is certainly frustrating when one receives a bug which is random and difficult to reproduce, imagine the frustration of the bug reporter who sees his report being downgraded or even closed (!) (see Bug #834964 for a very recent example) when it's quite clear that the package does not really "build from source". Thanks a lot.