Am Montag, den 30.05.2011, 12:08 +0200 schrieb Lucas Nussbaum: > On 30/05/11 at 12:04 +0200, Bruno Kleinert wrote: > > Am Montag, den 30.05.2011, 11:54 +0200 schrieb Lucas Nussbaum: > > > On 30/05/11 at 11:31 +0200, Bruno Kleinert wrote: > > > > Am Montag, den 30.05.2011, 09:26 +0200 schrieb Lucas Nussbaum: > > > > > On 29/05/11 at 22:48 +0200, Bruno Kleinert wrote: > > > > > > Am Sonntag, den 29.05.2011, 22:43 +0200 schrieb Bruno Kleinert: > > > > > > > Am Samstag, den 28.05.2011, 16:15 +0200 schrieb Lucas Nussbaum: > > > > > > > > Source: scorched3d > > > > > > > > Version: 43.2a.dfsg-2 > > > > > > > > Severity: serious > > > > > > > > Tags: wheezy sid > > > > > > > > User: debian...@lists.debian.org > > > > > > > > Usertags: qa-ftbfs-20110528 qa-ftbfs > > > > > > > > Justification: FTBFS on amd64 > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > During a rebuild of all packages in sid, your package failed to > > > > > > > > build on > > > > > > > > amd64. > > > > > > > I tried to reproduce the FTBFS in a freshly upgraded sid build > > > > > > > chroot > > > > > > > but scorched3d built just fine. Did you use any bleeding edge > > > > > > > packages > > > > > > > to build scorched3d to trigger this bug? > > > > > > Oops, I forgot to attach my build log. Here it is. > > > > > > > > > > Hi, > > > > > > > > > > You enabled parallel building in your debian/rules. Are you sure that > > > > > this is supported by the upstream build system? > > > > > > > > > > - Lucas > > > > Hi Lucas, > > > > > > > > I don't know if it is supported or not, as I never ran into any bugs > > > > building scorched3d in parallel. I greenly assumed it's supported by > > > > autotools, but maybe that's no good idea ;) > > > > > > > > A few minutes ago I started a job on my notebook (dual core, but only > > > > i386) to repeatedly rebuild scorched3d (sbuild --debbuildopt=-j2 ...). > > > > Let's see if it randomly fails at least once until the end of the day. > > > > > > > > Could you please try to rebuild scorched3d on your build cluster to try > > > > to reproduce a failing build? If it fails again, could you please try if > > > > it builds fine without the parallel option enabled? > > > > > > It failed twice in my initial rebuild, starting from scratch each time. > > Does it build fine with -j1 on your cluster? If so, I'll disable > > parallel builds in debian/rules. > > I don't have the time to investigate further, sorry. Ok.
I've built scorched3d ten times with up to a maximum of -j30 parallel jobs but was unable to provoke a failing build on a i386 dual core notebook. On my dual core amd64 machine I was also unable to produce a failing build. All builds were done in a clean up-to-date sid chroot environment. As I'm unable to provoke the reported bug, I'll tag this bug report as unreproducible. Cheers - Fuddl
signature.asc
Description: This is a digitally signed message part
