# from Nicholas Clark
# on Monday 10 September 2007 11:44 am:
>On Mon, Sep 10, 2007 at 11:37:00AM -0700, Eric Wilhelm wrote:
>> I was playing with the 't/' directory from perl-5.8.8 last night and
>> having very little luck. For starters, I had to hack t/TEST to
>> print the filenames, but still came up with 995 files instead of
>> 933, so I think I did it wrong ;-)
>
>In the core use the files as listed in MANIFEST
Hacking t/harness to do
system($^X, qw(-I /tmp/lib -S runtests -j 9), @tests);
in place of 'Test::Harness::runtests(@tests)' gets it rolling. (I know,
that could be App::Prove->new and not need the system(), but this is
essentially the same problem as parrot where the tests are organized
internally (by logic inside the t/harness file), which makes it hard to
run them with the standard runtests application.)
>I think that I documented this somewhere, but once you get to 7 tests
> in parallel, where you pass the tap stream back to a central
> parser/reporter, the parser in Test::Harness became the bottleneck.
If that's the case, I shouldn't be finding that -j 9 is the sweet spot
on a 2cpu box because TAP::Parser's parser is provably slower. Maybe
the core tests have more subtests than average?
--Eric
--
"Everything goes wrong all at once."
--Quantized Revision of Murphy's Law
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
