# from Andy Armstrong # on Monday 10 September 2007 11:13 am: >On 10 Sep 2007, at 19:12, Andy Armstrong wrote: >> What are the steps a parrot-n00b would take to be able to reproduce >> your results?
svn co https://svn.perl.org/parrot/trunk parrot perl Configure.pl make make test If your Test::Harness is 2.99_+, you'll see lots of places where the -I switch angers the '#!./parrot'. I tend to think this is an abuse of Test::Harness and therefore parrot should bundle Test-Harness-2.64 in their distro (at least, until they get away from it.) >Sounds like Eric's got it under control :) More or less (but there's only one of me.) From prove's point of view, the parrot test suite is a wreck in terms of how it defines which tests are to be run. Some are blacklisted, activated by options, etc. This logic is also (potentially) distributed to every $(find -name harness) file in the tree. So, this is only a *start* because it currently has no way to know which test files to run. http://scratchcomputing.com/tmp/runtests --Eric -- As an old bass player friend of mine used to say: throw money, don't clap. --Tony Parisi --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
