On Mon, Jan 20, 2014 at 7:17 AM, Adam Borowski <kilob...@angband.pl> wrote: > I repeated the build on an armhf box, all 3 tries succeeded. So did it on > all buildds for first-class architectures, while on the x32 buildd there > were two failures out of two attempts. It seems that the x32 buildd runs on > a good deal faster machine than i386 and amd64 ones: looking at some random > package, I see 25s:x32 vs 1m50s:i386. All other architectures are, > unsuprisingly, slower. > > So it's some timing issue. I have a strong hunch it's a bug in the test > suite rather than in the code being tested, so if it's tricky to debug, > disabling that test wouldn't be as bad an idea as papering over test > failures usually is. > > (Not sure what's the right severity for "FTBFSes on too fast". As my home > machines are not so hot, I went with "serious" as hardware only goes faster, > but you probably know better.)
Thanks for the report. It seems like this has popped up in Ubuntu as well. In conversation with upstream, they have decided to disable the test for now. [0] I think I'll probably end up doing the same here. [0] https://bugs.launchpad.net/debian/+source/bzr/+bug/1269886 Thanks! -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org