>>>>> On Fri, 27 Jan 2012 20:19:03 -0800, David Oswald <daosw...@gmail.com> >>>>> said:
> If you look at the static test summary page: > http://static.cpantesters.org/distro/I/Inline-CPP.html > you will see that v0.33_004 and 0.33_005 (especially the latter) have > begun failing miserably. Wrong. Inline-CPP 0.33_005 ( 234 ALL, 206 FAILs, 28 PASSes ) Inline-CPP 0.33_004 ( 12 ALL, 4 FAILs, 8 PASSes ) Inline-CPP 0.33_003 ( 47 ALL, 6 FAILs, 41 PASSes ) Inline-CPP 0.33_002 ( 24 ALL, 2 FAILs, 22 PASSes ) Inline-CPP 0.33_001 ( 26 ALL, 2 FAILs, 24 PASSes ) What this tells me is that you get more tst reports, not significantly less passes. The explanation to me is that Chris has started smoking your module and his installation fails, that's all. > The primary issue is illustrated in the > following report (it's easy to find a good example, as there are many > similar reports): > http://www.cpantesters.org/cpan/report/8e352ea2-488b-11e1-9d6f-f6dbfa7543f5 Yes, this one is from Chris. But Chris is not the only one sending fails. > Looking over the report you will see that test 00load_prereqs.t passes > ok. That test uses Test::More to do a "use_ok( 'Parse::RecDescent' ). > However, the next test: 01basic.t fails because it cannot find the > dependency Parse::RecDescent. > The 00load_prereqs.t test also spits out a "diag()" message that shows > the PERL5LIB environment variable so that I can confirm that the paths > look reasonable. But as I mentioned, the use_ok() test passes, while > the 01basic.t test (which invokes Inline::CPP, that in turn requires > Parse::RecDescent) fails. The easiest way to diagnose the reason would be to add a diag to your 00load_prereqs test that shows *where* Parse::RecDescent is found. As you can see here: http://analysis.cpantesters.org/reports_by_field?SUBMIT_xxx=Submit&distv=Inline-CPP-0.33_005&field=meta%3Afrom&field=qr%3A%28Can%27t+locate+\S%2Bpm%29&field=meta%3Afrom&field=meta%3Aperl&field=meta%3Awriter&field=mod%3ACPANPLUS%3A%3ADist%3A%3ABuild&field=mod%3AParse%3A%3ARecDescent&field=qr%3A%28Can%27t+locate+\S%2Bpm%29 All fail reports have Parse::RecDescent installed. But we d not see where. But we do see where it was not found: Can't locate Parse/RecDescent.pm in @INC (@INC contains: /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-0.49/blib/lib/ /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-CPP-0.33_005/blib/lib /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-CPP-0.33_005/blib/arch /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-0.49/blib/lib /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-0.49/blib/arch /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-0.49/blib/lib /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-0.49/blib/arch /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-CPP-0.33_005/blib/lib /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-CPP-0.33_005/blib/arch /home/cpan/pit/thr/perl-5.14.0/lib/site_perl/5.14.0/x86_64-linux-thread-multi /home/cpan/pit/thr/perl-5.14.0/lib/site_perl/5.14.0 /home/cpan/pit/thr/perl-5.14.0/lib/5.14.0/x86_64-linux-thread-multi /home/cpan/pit/thr/perl-5.14.0/lib/5.14.0 .) at /home/cpan/pit/thr/conf/perl-5.14.0/.cpanplus/5.14.0/build/Inline-CPP-0.33_005/blib/lib/Inline/CPP/grammar.pm line 16. Once you have the directory in which P:RD was found you can compare whether this directory was listed in the @INC variable that is dumped in the error diagnostics. > [...] > I've been soliciting assistance from the wise folks over at > inl...@perl.org, where Rob (sysiphus, maintainer of Inline and > Inline::C) suggested that possibly a recent upgrade to the smokers has > caused this problem for me. I'm also theorizing that CPANPLUS may be > at fault, though I can't figure out how so. Nope, Chris is only using CPANPLUS, but you find the same bug also from testers using CPAN::Reporter. > [...] Where do I go from here in resolving the problem? analysis.cpantesters.org is your friend when you have such questions. In this case I have not found a solution there but at least an answer. -- andreas
