IainS develo...@sandoe-acoustics.co.uk writes:
that's really neat indeed - I should have spotted the potential looking at
the code in contrib
... although the site.exp is hardwired in btest.sh at present ;
I guess one might be able to use .dejagnurc - just need to check on the
order that
On 10 Mar 2010, at 09:12, Rainer Orth wrote:
IainS develo...@sandoe-acoustics.co.uk writes:
that's really neat indeed - I should have spotted the potential
looking at
the code in contrib
... although the site.exp is hardwired in btest.sh at present ;
I guess one might be able to use
On 10 Mar 2010, at 09:22, IainS wrote:
Far easier: just set the DEJAGNU environment variable to the absolute
path to the size.exp file. runtest knows about that.
the DEJAGNU env. var is set in btest.sh
my mistake.
duh - that's what comes of working with code that was forked a long
time
IainS develo...@sandoe-acoustics.co.uk writes:
Far easier: just set the DEJAGNU environment variable to the absolute
path to the size.exp file. runtest knows about that.
the DEJAGNU env. var is set in btest.sh
It's not:
$ grep DEJAGNU contrib/regression/btest-gcc.sh
# DEJAGNU: should point
FWIW;
the bus errors were consistently coming from expect in a strcpy [about
100 tcl levels down]
the actual fault was a corrupted dejagnu installation - it's not clear
how that happened - nothing present in syslogs to indicate disk
problems.
a clean install of dejagnu appears to have
IainS develo...@sandoe-acoustics.co.uk writes:
on my mere 8 cores :-) I'm still getting sporadic Bus errors on:
make -k -j8 check RUNTESTFLAGS ...
[from the command line on a bootstrapped clean trunk @157307]
so there's something else wrong somewhere...
Probably make gets SIGBUS, which
On 9 Mar 2010, at 12:10, Rainer Orth wrote:
IainS develo...@sandoe-acoustics.co.uk writes:
Am I trying something that is unsupported - or is this is a bug?
===
make -k -j8 check is not particularly helpful (a) because it tests
gmp/mpfr/mpc every time (b) any redirected output is hard to
IainS develo...@sandoe-acoustics.co.uk writes:
Instead, run make mail-report.log afterwards and check that.
Although, I note that contrib/test_summary only reports what gets into the
*.sum files -- i.e. tests that complete or timeout.
It doesn't log problems in the actual make process itself
On 3/9/2010 4:28 AM, IainS wrote:
It would be nice to allow the apparently independent targets [e.g.
gcc-c,fortran,c++ etc.] to be (explicitly) make-checked in parallel.
On certain targets, it has been necessary to do this explicitly for a
long time, submitting make check-gcc, make
On 9 Mar 2010, at 12:46, Rainer Orth wrote:
IainS develo...@sandoe-acoustics.co.uk writes:
Instead, run make mail-report.log afterwards and check that.
... snip
suite in parallel, which isn't bad either.
As I wrote before, I'm going to use this on an (effectively) 64-core
machine and
IainS develo...@sandoe-acoustics.co.uk writes:
Am I trying something that is unsupported - or is this is a bug?
===
make -k -j8 check is not particularly helpful (a) because it tests
gmp/mpfr/mpc every time (b) any redirected output is hard to scan for
problems.
What you're trying is far
On 9 Mar 2010, at 19:13, Janis Johnson wrote:
To run all of the compiler tests in parallel you can do make -jn -k
check-gcc from the top level and let the existing build machinery
take care of running chunks of tests in parallel and putting the
results back together.
that's fine (I
On Tue, Mar 9, 2010 at 2:27 PM, IainS develo...@sandoe-acoustics.co.uk wrote:
I do build gmp/mpfr/mpc in-tree...
How? Last I tried, it didn't work, as mpc used the system gmp/mpfr,
not the just-built in-tree versions. Therefore, it's not really an
in-tree build, and you can't build on a system
IainS develo...@sandoe-acoustics.co.uk writes:
.. I don't seem to get the bus errors on a 4CPU g5 or a Core 2 duo .. but
.. the 8-core machine is faster .. so ... race conditions are more likely
to manifest there.
But race conditions don't manifest themselves in make SEGVs ;-( I'm
On 9 Mar 2010, at 19:31, NightStrike wrote:
On Tue, Mar 9, 2010 at 2:27 PM, IainS develo...@sandoe-acoustics.co.uk
wrote:
I do build gmp/mpfr/mpc in-tree...
How? Last I tried, it didn't work, as mpc used the system gmp/mpfr,
not the just-built in-tree versions. Therefore, it's not really
On 9 Mar 2010, at 19:36, Rainer Orth wrote:
IainS develo...@sandoe-acoustics.co.uk writes:
.. I don't seem to get the bus errors on a 4CPU g5 or a Core 2
duo .. but
.. the 8-core machine is faster .. so ... race conditions are more
likely
to manifest there.
But race conditions don't
16 matches
Mail list logo
