Re: [libvirt] [PATCH] build: drop a painfully long gnulib test

2012-03-21 Thread Michal Privoznik
On 21.03.2012 00:14, Eric Blake wrote: On machines with massive amounts of CPUs, the gnulib 'test-lock' could take minutes, or even appear to deadlock, because of timing interactions between multiple cores. See https://bugzilla.redhat.com/show_bug.cgi?id=797284. For precedence, note that

Re: [libvirt] [PATCH] build: drop a painfully long gnulib test

2012-03-21 Thread Eric Blake
On 03/21/2012 02:41 AM, Michal Privoznik wrote: On 21.03.2012 00:14, Eric Blake wrote: On machines with massive amounts of CPUs, the gnulib 'test-lock' could take minutes, or even appear to deadlock, because of timing interactions between multiple cores. See

[libvirt] [PATCH] build: drop a painfully long gnulib test

2012-03-20 Thread Eric Blake
On machines with massive amounts of CPUs, the gnulib 'test-lock' could take minutes, or even appear to deadlock, because of timing interactions between multiple cores. See https://bugzilla.redhat.com/show_bug.cgi?id=797284. For precedence, note that iwhd has done the same: