Guys,
Okay, just to follow-up in case anyone cared what the resolution on
this one was, changing the loop full of ok()s to one giant pass() or
fail() per loop fixed _everything_. Plus it runs a lot faster now. I
know I've seen test suites that do thousands and thousands of tests,
but they must
On 2011.11.15 1:14 AM, Buddy Burden wrote:
Okay, just to follow-up in case anyone cared what the resolution on
this one was, changing the loop full of ok()s to one giant pass() or
fail() per loop fixed _everything_. Plus it runs a lot faster now. I
know I've seen test suites that do
On Mon, Oct 31, 2011 at 06:17:37PM -0700, Buddy Burden wrote:
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
David,
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.
No, but there are testers who have watchdog processes to kill off
anything that runs for an
On Tue, Nov 01, 2011 at 10:48:43AM -0700, Buddy Burden wrote:
David,
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.
No, but there are testers
David,
I guess I'm not sure what to do here. What do other folks advise?
Contact the individual testers, I guess.
I'm not sure what to say though ... hey, dude, your automated testing
is being rude to my tests, so go fix that? I mean, I wouldn't put it
that way, obviously, but i can't help
On Tue, Nov 1, 2011 at 12:56 AM, Buddy Burden barefootco...@gmail.com wrote:
t/rand_time.t (Wstat: 9 Tests: 1764021 Failed: 0)
Non-zero wait status: 9
*** Signal 9
That one is obvious, it has been SIGKILLed. Probably the tester
thought the tests were hanging.
t/rand_time.t
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
