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 who have watchdog processes to kill off > > anything that runs for an unfeasibly long time. > Okay. I guess the next question then is: what constitutes "an > unfeasibly long time"? Looks like the full version of this test file > takes around 200 seconds ... on my machine. Other people's machines > ... who can say? > > I guess I'm not sure what to do here. What do other folks advise?
Contact the individual testers, I guess. > > I start my test runs manually, and then just leave them running in the > > background. Every so often I check on them, and if one of them appears > > to have got stuck I give it a kick. > Hmmmm .... well, a standard "make test" would indeed appear to be > stuck, in that test files don't have any output until either a test > fails or they're all done. This seems to vary from one place to another - I'm not sure exactly what the differences are that cause it, but in some places some of my long-running tests *do* output some kind of count of how far they've got, and in some they don't. It's probably something to do with output buffering. > OTOH, the test itself is spitting out > "ok"s at what is most likely a furious rate ... it's just that > Test::Harness is eating them all. And what, dare I ask, constitutes a > "kick"? :-D Control-C. But I don't just do it if nothing appears to be happening. But if there's no change in several minutes then I might do it. -- David Cantrell | London Perl Mongers Deputy Chief Heretic If you can read this, thank a teacher. If you're reading it in English, thank Chaucer.