Andreas Koenig <andreas.koenig.7os6v...@franz.ak.mind.de> writes: > Karen Etheridge <et...@cpan.org> writes: > >>> If you can point us at a couple of example failure reports, maybe >>> someone here can figure out what's going wrong. In my experience it is >>> almost always the case that things like this are caused by an error in >>> the distribution under test. >> >> Here's the most recent example of such failures: >> http://www.cpantesters.org/cpan/report/cb01432c-6737-11e2-992e-e7c00a4a7996
I have contacted Nigel and he sent me his CPAN.pm configuration and I cannot see anything wrong in it. Especially my suspect about trust_test_report_history was wrong, trust_test_report_history is off. >> As you can see, only the configure_requires dependencies have been >> installed. I fear this is a misleading sentence, because fact is only that the PREREQUISITES section of the report is too short. Normally CPAN::Reporter tells us more about installed prerequisites. From this fact we cannot make generalized assumptions about Nigel's installation. >> *Some* of the runtime requirements are in @INC via their blib >> directories, but not all -- and the compilation tests fail immediately >> because Moose is one of the missing dependencies. Moose is clearly >> identified as a prereq in the metadata, both a v1.4 META.yml and a v2.0 >> META.json file and Makefile.PL. Well, I have tried to get my perl 5.8.1 to install Moose and it fails early because Moose demands 5.8.3. After that CPAN::Reporter refused to write a test report because of missing prerequisites. And this is what we expect. At the moment I have no further ideas which bug or misconfiguration might have let the report escape that you encountered. Ideas, anybody? -- andreas
