Saturday February 23, 2008
11:12 PM
That damned Test::More threading test
I did it. I finally killed that damned threading test in Test::More. is_deeply_fail.t will no longer run unless AUTHOR_TESTING is set.
For those who don't know, that test would tickle intermittent threading bugs in certain vendor supplied versions of perl. The 5.8.6 OS X ships with and most Redhat derivatives are vulnerable, but it would only fail about one in a hundred times. I don't know what the problem is, I suspect it's from vendors pulling in bleadperl patches but I haven't confirmed. Nobody's put the time into it to find out.
Since there's nothing I can do about it, and it was just holding up CPAN installations, I turned the test off. Done.
Why AUTHOR_TESTING? (Score:1)
AUTOMATED_TESTING instead?
Re: (Score:2)
That's very much a mixed bag. On one hand, yes, you clearly would want it in those tests. On the other, it's not confidence inspiring to see a lot of test failures when you're evaluating a module. Of course, people say "yes, but you should check to see
Silence is Evil [easystreet.com]
Re: (Score:2)
There's only so many times I can say "don't use Redhat's (or any distribution derive
Re: (Score:1)
No, the point is, if there is an actual regression that these tests would catch, on a platform you don’t have, you won’t know about it if the CPAN Testers don’t run those tests.
How much of a concern that is depends on the tests in quest