Unreliability of the build system

[Geoffrey Mainland]

No, it's all done on a local (ZFS) file system (I don't even have any
NFS volumes mounted), although I *am* using a separate build tree.

Geoff

On 06/28/2013 10:30 AM, Simon Marlow wrote:
> Geoff - is it possible that this problem might be caused by time skew
> between NFS servers?  Are any parts of the build, or files accessed by
> it, on NFS?
>
> Cheers,
>     Simon
>
> On 24/06/13 23:44, Geoffrey Mainland wrote:
>> On 06/24/2013 09:21 PM, Jan Stolarek wrote:
>>>> My only claim was that I have a set of steps that can reliably
>>>> reproduce
>>>> an error on my system, not that these steps will reliably reproduce it
>>>> on an arbitrary system, e.g., yours. Still, being able to reliably
>>>> reproduce an error, even if only on one system, is *very* useful.
>>>   just misunderstood your use of the word "reliable". Certainly having
>> this level of
>>> reproducibility is very helpful in debugging, even if it's only on one
>> machine.
>>>
>>>> So, to be clear, you see recache errors sporadically and for different
>>>> sets of tests across different runs, and you are running validate with
>>>> no extra arguments, single-threaded, on a Linux x86_64 system with an
>>>> ext4 file system?
>>> Yes, except I would say "very often" instead of "sporadically". I'm
>> not sure about
>>> single-threaded. I run validate without any parameters - doesn't it
>> use more then one thread in
>>> this case?
>>
>> It looks like running validate without any parameters will use 2
>> threads.
>>
>> I've pushed a fix (I hope) for this issue. Could you check and see if
>> it's fixed for you now?
>>
>> Geoff
>>
>>
>>
>> _______________________________________________
>> ghc-devs mailing list
>> ghc-devs at haskell.org
>> http://www.haskell.org/mailman/listinfo/ghc-devs
>>
>