Re: test-lock taking a long time?

[Eric Blake]

On 01/25/2012 02:45 AM, Jim Meyering wrote:
> Simon Josefsson wrote:
> 
>> Has anyone noticed that test-lock takes a long time to complete on some
>> systems?  On my laptop it is fast:
> ...
>> However on a otherwise idle machine with 2xE5520's (resulting in 16
>> virtual CPUs), it takes much longer:
>>
>> address@hidden:~/gnutls-3.0.12/gl/tests$ time ./test-lock
>> Starting test_lock ... OK
>> Starting test_rwlock ... OK
>> Starting test_recursive_lock ... OK
>> Starting test_once ... OK
>>
>> real 1m49.893s
>> user 1m31.874s
>> sys  16m4.056s
>> address@hidden:~/gnutls-3.0.12/gl/tests$

Another report of the same problem:
https://bugzilla.redhat.com/show_bug.cgi?id=797284

> Yes, I have seen precisely that problem, and it prompted this change in iwhd:
> 
> commit 8aa5b7111e46db425414ae33d5c07cef411e4630
> Author: Jim Meyering <address@hidden>
> Date:   Mon Mar 21 09:45:01 2011 +0100
> 
>     tests: skip annoyingly long gnulib lock tests
> 
>     * bootstrap.conf (avoided_gnulib_modules): Skip the lock tests.
>     They take too long.

I'll probably end up doing the same thing in libvirt, unless we can
figure out why the test is taking so long.

-- 
Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature