>>>>> On Sat, 29 Dec 2007 20:18:17 -0600, Elliot Shank <[EMAIL PROTECTED]> said:
>> Output from '/usr/bin/make test':
>>
>> PERL_DL_NONLAZY=1 /usr/local/perl-5.6.2/bin/perl "-MExtUtils::Command::MM"
>> "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
>> t/20_policy_podspelling.....................Fehler: No word lists can be
>> found for the language "de_DE".
>> Fehler: No word lists can be found for the language "de_DE".
>> Failed 4/4 subtests
> Dammit. I thought I had solved this.
> Would you mind sending me complete output from t/20_policy_podspelling.t in
this environment?
> Thanks.
Note that this happened under 5.6.2. Under all my other perls it was a PASS.
% make test TEST_FILES=t/20_policy_podspelling.t TEST_VERBOSE=1
PERL_DL_NONLAZY=1 /usr/local/perl-5.6.2/bin/perl "-MExtUtils::Command::MM"
"-e" "test_harness(1, 'blib/lib', 'blib/arch')" t/20_policy_podspelling.t
t/20_policy_podspelling......
1..4
Fehler: No word lists can be found for the language "de_DE".
Fehler: No word lists can be found for the language "de_DE".
Failed 4/4 subtests
Test Summary Report
-------------------
t/20_policy_podspelling.t (Wstat: 13 Tests: 0 Failed: 0)
Parse errors: Bad plan. You planned 4 tests but ran 0.
Files=1, Tests=0, 1 wallclock secs ( 0.02 usr 0.00 sys + 1.14 cusr 0.10
csys = 1.26 CPU)
Result: FAIL
Failed 1/1 test programs. 0/0 subtests failed.
make: *** [test_dynamic] Fehler 11
Let's see which harness version:
% /usr/local/perl-5.6.2/bin/module_info Test::Harness
Name: Test::Harness
Version: 3.05
Directory: /usr/local/perl-5.6.2/lib/5.6.2
File: /usr/local/perl-5.6.2/lib/5.6.2/Test/Harness.pm
Core module: yes
And which Test::More?
% /usr/local/perl-5.6.2/bin/module_info Test::More
Name: Test::More
Version: 0.74
Directory: /usr/local/perl-5.6.2/lib/5.6.2
File: /usr/local/perl-5.6.2/lib/5.6.2/Test/More.pm
Core module: yes
For good measure I tried to bring 5.6.1 in the game but interestingly
it failed on Pod-Parser-1.35.
So which Pod::Parser does my 5.6.2 have?
% /usr/local/perl-5.6.2/bin/module_info Pod::Parser
Name: Pod::Parser
Version: 1.3
Directory: /usr/local/perl-5.6.2/lib/5.6.2
File: /usr/local/perl-5.6.2/lib/5.6.2/Pod/Parser.pm
Core module: yes
And Pod-Parser 1.34 is the last to succeed on 5.6.1. With that we see
Perl::Critic succeed.
So the question remains, which Pod::Parser should you declare PREREQ.
[...time passes...] 1.31,1.32 are not enough. 1.33-1.35 fail their own
tests. Sigh. When I force-install 1.33,1.34,1.35 then
Perl-Critic-1.081_005 still fails.
Interestingly, when I downgrade Pod::Parser in 5.6.1 to 1.32, then
Perl-Critic-1.081_005 still succeeds. So you apparently can live with
1.32
Apparently Pod::Parser has a problem with my 5.6.2 and cannot be
upgraded above 1.32. But when I try to step through the failing test,
I get lost in forking and get no useful diagnostics. On cpantesters I
see that Pod::Parser 1.34 has both PASS and FAIL with 5.6.2 but 1.35
has only FAILs.
Hrmm. I'm running out of wit and patience right now. Let me know if
you find further facts that lead out of this maze:)
--
andreas
