Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

That damned Test::More threading test 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Surely you want it in the CPAN Testers tests?

    AUTOMATED_TESTING instead?

    • 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 what causes those failures", but this is problematic. Many, many times I've received a failure report with absolutely no information about why something has failed. Or I get a failure report with spurious information, which is just as annoying.

      If Schwe

    • Surely you want it in the CPAN Testers tests?
      They're not telling me anything I don't already know, there's nothing I can do about it and it's highly intermittent. Takes dozens or hundreds of runs before it shows up.

      There's only so many times I can say "don't use Redhat's (or any distribution derived from Redhat) perl".

      • 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 question.

        Intermittent failures from CPAN Testers should be easy to ignore, in any case.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.