Leon, >>> *** Signal 9 > > That one is obvious, it has been SIGKILLed. Probably the tester > thought the tests were hanging.
Well, that's probably the most common error ... surely there can't be _that_ many CPAN Testers folks hanging around actually _watching_ the tests run and killing them when they take too long. Typically CPAN Testers testing is done in an automated fashion, no? And, anyway, if you _were_ going to run the tests manually, you wouldn't turn on $AUTOMATED _TESTING, would you? >>> t/rand_time.t (Wstat: 139 Tests: 996881 Failed: 0) >>> Non-zero wait status: 139 >>> Parse errors: No plan found in TAP output > > If you're using done_testing, you should explicitly have a test/build > requirement on Test::More 0.88. Ah, yes, I should have mentioned that: I did indeed forget to do that the first time, but the latest dev version has that corrected. In fact, the CPAN Testers giving me the above error all have the same version of Test::More that I have (0.98), and a version of Test::Harness that was actually _newer_ than mine (3.23), although I upgraded and retested on my side just to make sure that wasn't it. >>> Out of memory! >>> Segmentation Fault - core dumped >>> make: *** [test_dynamic] Error 139 > > Yeah, Test::Builder maintains some state for every test result. See > https://metacpan.org/module/Test::Builder#MEMORY for some suggestions > on how to handle that. Cool, I'll check that out. -- Buddy
