Re: not sure what changed in testing

2009-02-17 Thread Eirik Berg Hanssen
mer...@stonehenge.com (Randal L. Schwartz) writes: plan 'no_plan'; BEGIN { use_ok('File::Finder') } These lines passed when I wrote them a few years ago. Is this: (a) an error in test reporter (b) an error in my code because this once worked but is now deprecated (c) an

not sure what changed in testing

2009-02-17 Thread Randal L. Schwartz
According to http://www.nntp.perl.org/group/perl.cpan.testers/2009/02/msg3293765.html the lines that are failing are (from http://github.com/RandalSchwartz/perl-module-file-finder/blob/06054daba44df857bf31e960032a53aa36237b0f/t/04-ffr.t): #! perl use Test::More; BEGIN {

Re: Your W3C-LinkChecker test reports

2009-02-17 Thread Chris 'BinGOs' Williams
On Tue, Feb 17, 2009 at 09:15:21AM +0200, Ville Skytt? wrote: Hi bingos, Howdy. Thanks for running the CPAN automated tests. However, I have a question regarding your numerous failure reports on W3C-LinkChecker 4.4: All the failure reports from you fail in the test suite with Can't

Re: Your W3C-LinkChecker test reports

2009-02-17 Thread David Golden
On Tue, Feb 17, 2009 at 9:06 AM, Chris 'BinGOs' Williams ch...@bingosnet.co.uk wrote: In your test I see that you use '-T' switch which makes perl ignore PERL5LIB, hence the blarting about can't find LWP/RobotUA.pm in @INC. Now, I thought CPANPLUS ( which I smoke on ) and CPAN used the same

Re: Your W3C-LinkChecker test reports

2009-02-17 Thread David Cantrell
On Tue, Feb 17, 2009 at 02:06:33PM +, Chris 'BinGOs' Williams wrote: Okay, I think the key phrase here is 'installed'. What we do in the test environment is resolve all the dependencies for a given module and the build_dir/blib/* directories get added cumulatively to PERL5LIB. Some of us

A note on the righ way of declaring dependencies (was: Your W3C-LinkChecker test reports)

2009-02-17 Thread Aristotle Pagaltzis
Hi Ville, * Chris 'BinGOs' Williams ch...@bingosnet.co.uk [2009-02-17 15:10]: On Tue, Feb 17, 2009 at 09:15:21AM +0200, Ville Skytt? wrote: All the failure reports from you fail in the test suite with Can't locate LWP/RobotUA.pm in @INC [...]. I'm wondering why this happens, because