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

use Perl Log In

Log In

[ Create a new account ]

drhyde (1683)

drhyde
  (email not shown publicly)
http://www.cantrell.org.uk/david

Journal of drhyde (1683)

Monday April 23, 2007
07:08 AM

Duplicate test results

[ #33072 ]

One thing that's a bit annoying about my CPAN testing environment is that it doesn't keep track of previous test results. This means that it sends duplicate PASS results for common pre-requisites like this and this. At least the default setting is to ask me before sending FAIL results, so I can manually check what I've sent before and avoid pissing authors off.

But no more! I've patched my local installation of CPAN::Reporter to not send duplicates and sent the diff to the author. If you want it before Dave uploads a new release to the CPAN, let me know.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Now if you were using CPAN::YACSmoke you wouldn't have this problem, as it automatically records the distributions you're testing. Hence why I'd like to add CPAN support and not have it tied to CPANPLUS as it is at the moment.
    • My understanding is that CPANPLUS uses Build.PL by preference even when a Makefile.PL is present. CPAN.pm, of course, prefers to use Makefile.PL. If everyone were to use CPANPLUS, then we wouldn't catch errors like this [perl.org] where the author lists all her dependencies in the Build.PL but her Makefile.PL is horribly out of date.
      • Not true. You can choose you use Makefile.PL as a preference in CPANPLUS. I'm glad it does as I am not a fan of Module::Build, mainly due to the fact it can't install itself, thus causing numerous crashes and fails for distributions when I was CPAN Testing on Windows.

        One idea I've had more recently is to incorporate some standard testing in YACSmoke, so that rather than the distribution including tests for testing POD [cpan.org], POD coverage [cpan.org], Meta.yml [cpan.org] or the whole distribution [cpan.org] and possibly even the complete test sui [cpan.org]

  • 0.42 is uploading to CPAN now with the new "send_duplicates" option. Duplicate reports will be skipped by default, but this behavior may be customized similar to most other CPAN::Reporter configuration options.
  • IMHO, such code should also check for prerequisites versions - it may fail with some combinations. And in some distant future - versions of C libs.