Once I get around to checking-in these changes, the following becomes an 
option:

  ./Build test --tap-harness-args jobs=29 --use-tap-harness

Unfortunately, that only cuts the test time from 22 to 15s for me.  I 
notice that t/compat.t is using 8s, most of which is spent doing the 
same steps in different variations.

My preferred way to speed up the compatibility testing would be to 
delete t/compat.t, but perhaps a more conservative developer would like 
to break the test_makefile_types(); step into 6 separate files?

Thanks,
Eric
-- 
To a database person, every nail looks like a thumb.
--Jamie Zawinski
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------

Reply via email to