On Mon, Sep 19, 2005 at 02:25:01PM +1000, Sisyphus wrote: > One not-so-nice feature of this is that if one of the tests for a particular > module fails, then 'make test' stops, and the tests for the remaining > modules do not get run. How could that behaviour be changed (so that *all* > tests get run, irrespective of how many failures there are) ?
There is, AFAIK, no easy way to do this. "make test" is simply recursing into the subdirectories and running "make test" again. Ignoring the exit code of those tests would mean the top level "make test" would not exit with non-zero and it would appear as if the tests passed. You can try overriding test_via_harness() so it runs all the tests in one shot <insert hand waving here>. Or you can disolve the bundle. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that which, when you stop believing in it, doesn't go away. -- Phillip K. Dick
