As of TAP::Harness r465, the --jobs switch to prove enables parallelization of your test suite.
http://svn.hexten.net/tapx/trunk http://scratchcomputing.com/svn/TAP-Harness-Parallel/trunk Note that your test suite may or may not play nicely with that. Have you ever run them in parallel before? ;-) Assuming common tempfiles and such really rains on the parade. Other than that, we're talking 40% less waiting. I think I should maybe support bail_out before that goes on CPAN. Can anyone find any other major issues? Note, -j 9 seems to be the sweet-spot on most 2cpu machines. Resources (disks, memory, databases, etc.) tend to keep more from being useful and I/O latency (or something along those lines) tends to make less not so great either. Bonus points if you have pointers about usable copy-on-write networked filesystems and/or you come up with lyrics of 'prove -j 9' as a parody of "kill dash nine." :-D --Eric -- software: a hypothetical exercise which happens to compile. --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
