Re: [patch] testsuite: pthread_cond_wait.exp: Avoid a race

[Tom Tromey <tromey@redhat.com>]

Joel> OK, it will be fine, I suppose, especially if we can file-parallelize
Joel> the testsuite.

I have it working -- not in my totally ideal form, but I'm reaching
diminishing returns and also boredom.  I need to look into some
remote-testing things, and also write up an RFC about changes to the
tests.  I keep postponing this, mostly due to unrelated things, but I'll
get to it sooner rather than later.

Anyway, as part of this, I looked at test suite timings.  I ran each
.exp file separately and looked at the elapsed time it took.

Some interesting bits:

octave:3> mean(Tdata)
ans =  1.1680
octave:4> min(Tdata)
ans =  0.070000
octave:5> max(Tdata)
ans =  80.780
octave:6> std(Tdata)
ans =  4.1273

So, most tests are quite fast, but we have some huge outliers.  The 80
second one is break-interp.exp, but there are others, see appended.

Crunching the numbers, something I'm not totally confident I did
correctly, says that we can scale the test suite up to about -j12.
After that break-interp will start dominating the time.

Tom

All times further than 2 standard deviations from the mean:

octave> sort(Tdata(find(Tdata > mean(Tdata) + 2*std(Tdata))), 'descend')
ans =

   80.7800
   60.4900
   40.2700
   34.3500
   22.0500
   20.0000
   19.8900
   19.6500
   19.3000
   15.4500
   14.7300
   14.5400
   13.5700
   10.2300
    9.9100
    9.7000