On 31/03/12 at 22:11 -0400, Yaroslav Halchenko wrote: > Hi Lucas, > > I strongly believe that this one is a false positive and has to do with > a peculiarity of the build farm setup or load. I have rebuilt in > a clean up-to-date cowchroot and a dirty up-to-date chroot on my laptop > -- both built just fine. > > Similar (same FTBFS failure from Grid'5000) bug reports were > opened/closed before: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652231 > > so, it might be that it is worth looking into it deeper if such failures > are reproducible... if they are not reproducible -- might be worth > adding them to some kind of 'ignore' list or if possible just redoing > the build to see if the FTBFS is any consistent. > > Cheers,
Hi, Note that, despite what the footer in the bug report says, I've switched to using Amazon EC2 for my archive rebuilds, and the build env is completely new. I retried building cython. It failed once, but succeeded once: > runTest (__main__.CythonRunTestCase) > compiling (c) and running r_jeff_epler_1 ... blowup (line 1) > (r_jeff_epler_1.__test__) > Doctest: r_jeff_epler_1.__test__.blowup (line 1) ... ok > runTest (__main__.CythonRunTestCase) > compiling (cpp) and running r_jeff_epler_1 ... make: *** wait: No child > processes. Stop. > make: *** Waiting for unfinished jobs.... > make: *** wait: No child processes. Stop. > semop(2): encountered an error: Invalid argument > semop(1): encountered an error: Invalid argument > Build killed with signal TERM after 15 minutes of inactivity There might be a random bug somewhere. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
