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 - to find those
> one still has to trawl through the interleaved stuff.
No, you haven't. You need to look at the corresponding *.log files
instead; most of this isn't in the regular make check output anyway.
> It would be nice to allow the apparently independent targets [e.g. gcc-
> c,fortran,c++ etc.] to be (explicitly) make-checked in parallel.
This is exactly what happens when you invoke make -j<N> -k check,
provided that the parallelism specified is big enough (and the machine
can handle the load). Otherwise, you may end up running (say) the c
testsuite in parallel, which isn't bad either.
As I wrote before, I'm going to use this on an (effectively) 64-core
machine and hope to achieve to use all cores in parallel :-)
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
