[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: test-lock taking a long time?

From: Jim Meyering
Subject: Re: test-lock taking a long time?
Date: Wed, 25 Jan 2012 10:45:38 +0100

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$
> Is there some scaling in the test that makes it take longer for
> multi-cpu machines?  I didn't see any from a quick look.
> For comparison, my laptop is running debian squeeze and the multi-CPU
> machine is running Ubuntu 11.10 (i.e., libpthread is used on both
> machines).

Hi Simon,
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.

diff --git a/bootstrap.conf b/bootstrap.conf
index c64c7ac..930ebda 100644
--- a/bootstrap.conf
+++ b/bootstrap.conf
@@ -15,6 +15,12 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.

+# The lock test takes too long for my taste.
+  --avoid=lock-tests
+  --avoid=dummy
 # gnulib modules used by this package.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]