Hei!
Looking forward to the hackathon this weekend! :)
Just to make it a little more fun/productive, my colleagues and I are bringing
some code to show you all! :D
We're bringing a functioning post-install test extension for Module::Build. The
main features are:
- With it, you can
This is great news, I know a few people who wanted this for a long
time. I'm not coming for this hackathon, so please publish slides and
discussion notes afterwards.
On the scale between proof-of-concept and production-ready, where does
your code fall?
So far, have any considerations been made
Nicholas,
tl;dr: TAP::Harness uses lots of RAM to store test results
Particularly lots and lots for millions of little ok\ns
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
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\ns
It would be nice if it didn't use lots of RAM when storing things that
mostly
pass.
Yes, I ran
