On Thu, Sep 23, 2010 at 3:14 AM, Sisyphus <[email protected]> wrote: > But if it's a matter of getting the failing test to pass, then that's > something else. I tried to put some diagnostic messages into > contrib/automated_pp_test.pl and then re-run 'perl -Mblib t/20-pp.t', but > inc/Test/Builder.pm won't let me do that. (Perhaps someone else here knows > the way to work around that problem. All I get is "# No tests run!")
The canonical way to run just a single test (with more diagnostic output) is make TEST_VERBOSE=1 TEST_FILES=t/20-pp.t > But if we can't readily modify automated_pp_test.pl, then the > task is not as simple as one would like. BTW, automated_pp_test.pl is obviously a generated file, but the source seems to be lost. That makes it very hard to modify it or add a new test. > In any case, I suspect it's a bug in the test script that's causing the > failure (which I can't reproduce on Windows Vista, btw). So I would just do > 'cpan -fi PAR::Packer'. Please don't advise users to "force install" PAR::Packer. You may be right that the failing test is a glitch in the test suite. But it may also be caused by a genuine bug in PAR::Packer that will bite the user later. Cheers, Roderich
