On Wed, Jan 14, 2009 at 11:42:46PM +0100, Mazen NEIFER wrote: > Le mercredi 14 janvier 2009 à 19:43 +0100, Kurt Roeckx a écrit : > > On Wed, Jan 14, 2009 at 12:04:34AM +0000, peter green wrote: > [...] > > It was succesful on one of the buildds (and got uploaded) and failed > > on the other. And I see no reason why it should fail on the other. > > Is it possible to try a second time on the same buildd to see if the > problem is random or systematic? As the debug symbols were not included, > the given stack trace is really useless. > > > I can only assume either the buildd chroot isn't clean or it's some > > kernel issue. The buildd with the problem is running a 2.6.26 kernel. > > Or it may be a register allocator non deterministic issue. I had such an > issue for sparc : one time out of three, the compiler could not rebuild > itself. May be this one is similar.
All failed attempts where on the same buildd host. So I assume it's something related to that host and not the package. I will try and take a closer look in the weekend. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
