# from Parrot via RT
# on Tuesday 04 September 2007 01:30 am:

>With TAP::Parser, the attached patch and Parrot/TAP/Harness.pm in the
>current directory[1], the tests can be run as:
>
>  runtests --harness Parrot::TAP::Harness $(perl t/harness --files)

The runtests code has been refactored into App::Prove, which allows 
parrot to make their own ./runtests such as the attached.  This gets 
rid of the need for --harness argument, and also allows for additional 
argument flag customizations.

  ./runtests $(perl t/harness --files)

Get TAP::Harness from the svn.  Note: this distro also contains a 
lib/Test/Harness.pm and bin/prove -- neither of those are needed for 
this, and they *might* even cause trouble with the existing parrot test 
framework.

  http://svn.hexten.net/tapx/trunk

Additionally, there is now parallel testing support with 
TAP::Harness::Parallel.

  http://scratchcomputing.com/svn/TAP-Harness-Parallel/trunk

This works like:

  ./runtests --jobs 9 $(perl t/harness --files)

And appears to yield a 30-40% decrease in wait time (assuming that tests 
do not have resource conflicts (shared tempfiles, etc.))  A cursory 
examination implies that some parrot tests do indeed have such 
conflicts, but you have to crank -j up to 25 to find them (which is 
borderline forkbombing.)

  t/pmc/io.t
  t/pmc/os.t
  t/dynoplibs/myops.t
  t/src/extend.t

--Eric
-- 
Like a lot of people, I was mathematically abused as a child.
--Paul Graham
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------

Attachment: runtests
Description: Perl program

Reply via email to