Federico Beffa writes:
> On Thu, Dec 11, 2014 at 2:20 PM, Ludovic Courtès wrote:
>> Check if that flag has an effect at all. For instance,
>> Automake-generated makefiles have supported parallel test suites for
>> not-too-long (a couple of years maybe) and even there it’s optional.
>> Hand-writ
On Thu, Dec 11, 2014 at 2:20 PM, Ludovic Courtès wrote:
> Check if that flag has an effect at all. For instance,
> Automake-generated makefiles have supported parallel test suites for
> not-too-long (a couple of years maybe) and even there it’s optional.
> Hand-written build systems often run tes
Federico Beffa skribis:
> Thanks for the input! It looks like on hydra the failure is
> reproducible.
It’s actually hard to know, because guix-daemon on hydra.gnu.org runs
with --cache-failures.
> Now that you mention race conditions, I remember having a hard time
> with parallel builds in ATLA
Federico Beffa writes:
> On Wed, Dec 10, 2014 at 7:33 PM, Mark H Weaver wrote:
>> It's not uncommon for some tests to fail occasionally in certain
>> packages. Reasons I've seen include: timeouts set too short, race
>> conditions, randomized tests that fail for some values, and dependencies
>>
On Wed, Dec 10, 2014 at 7:33 PM, Mark H Weaver wrote:
> It's not uncommon for some tests to fail occasionally in certain
> packages. Reasons I've seen include: timeouts set too short, race
> conditions, randomized tests that fail for some values, and dependencies
> on the kernel version and/or co
Federico Beffa writes:
> I've noticed that on hydra python2-numpy-1.9.1 for x86_64-linux (and
> other architectures) fails to pass the test procedure (really the
> module local version without documentation called
> python2-numpy-bootstrap-1.9.1):
>
> http://hydra.gnu.org/build/172563
>
> So, I'v
