Magnus Hagander wrote:
>> In fact, on the last run of each, MinGW was by far the slowest and
>> Cygwin the fastest in the "make check" step. But there could be any
>> number of reasons for that, including extraneous activity on the VM host
>> that could have slowed the whole VM down.
>>
>
> Yeah. It does surprise me a lot that cygwin should be fastest, really.
>
>
>
Don't read anything into it. The VMware clock is quite unreliable, in my
experience.
cheers
andrew
