On Thu, Apr 11, 2013 at 10:24:35AM -0700, Buddy Burden wrote: > Nicholas, > > tl;dr: TAP::Harness uses lots of RAM to store test results > > Particularly lots and lots for millions of little "ok\n"s > > It would be nice if it didn't use lots of RAM when storing things that > > mostly > > pass. > > > > Yes, I ran into this before.(*) I was referred to a portion of the > Test::Builder POD(**) which says that perhaps it will be fixed one day. > :-D I guess "one day" hasn't come yet ... > > Perhaps some of these references will inspire someone with enough tuits to > work on a patch ... ? > > > -- Buddy > > (*) http://code.activestate.com/lists/perl-qa/12708/ > (**) https://metacpan.org/module/Test::Builder#MEMORY
I don't think that I hit the same problem as you. It wasn't actually Test::Builder that was bailing out from inside a test script. It was some part of Test::Harness or TAP::Parser in the harness process that was running the scripts, and collating the results of all the TAP, that was failing for me. And yes, I'm rather hoping that someone will think that as this is an optimisation project, it's fun. The code is here: https://github.com/Perl-Toolchain-Gang/Test-Harness Nicholas Clark
