Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • When I see a FAIL on search.cpan, I usually click on the link to see what failed. The reports returned by YACSmoke are very long, but they lack the information I want: the details of which test, in which test script, failed.

    See [] for example.

    Thanks in advance. :-)

    • This is a problem with the new CPANPLUS rather than CPAN::YACSmoke. To get the test run for reports you switch verbose mode on. As such it then gives you everything! However, I'm already looking to add an option to CPAN::YACSmoke to filter the 'Extracted' messages.

      It's also a know problem [] that a distribution with pre-requisites can produce the test run for all in all reports within that test run.

      Another problem, which is the problem you've unknowingly spotted, is that CPANPLUS doesn't currently catch the 'perl Makefile.PL/Build.PL' failures. However, I'm compiling the patch and tests for that at the moment.

      I realise that CPAN::YACSmoke is probably going to get the most stick for test reports that aren't correct, but bear in mind there is a huge framework that actually does the work.