[auf englisch, wegen der Verteilung an cpan-testers]

On 3 Nov 01, at 21:40, Gerrit P. Haase wrote:

> Am 2001-10-28 um 07:24 schriebst du:
> 
> > On 28 Oct 01, at 1:43, Gerrit Haase wrote:
> 
> > Which version of Test::Harness are you using? I have 1.25 and it does not
> > mark any tests as failed, since it recognises the 'TODO' part of the output.
> > Here is the relevant bit of the output as produced on my system (with
> > Test::More v0.32):
> 
> I have one more for Test::More, but much less for Test::Harness:
> 
> Module id = Test::Harness
>     DESCRIPTION  Executes perl-style tests
>     CPAN_USERID  P5P (The Perl5 Porters Mailing List <[EMAIL PROTECTED]>)
>     CPAN_VERSION undef
>     CPAN_FILE    Contact Author The Perl5 Porters Mailing List 
><[EMAIL PROTECTED]
>     DSLI_STATUS  Supf (standard,comp.lang.perl.*,perl,functions)
>     MANPAGE      Test::Harness - run perl standard test scripts with statistics
>     INST_FILE    /usr/lib/perl5/5.6.1/cygwin-multi/Test/Harness.pm
>     INST_VERSION 1.1604

Strange that CPAN_VERSION is 'undef'. http://search.cpan.org/ gives 
version numbers for the Test::Harness in Perl 5.003_07 (1.13), 
5.004_05, 5.005_03, 5.6.1-trial3 (all 1.16), and 5.7.2 (1.21).

And version 1.25 is in the distribution Test-SDK-0.04 from Schwern's 
directory (should be authors/id/M/MS/MSCHWERN). Perhaps you could try 
that?

> cpan> install Test::Harness
> CPAN: Storable loaded ok
> Going to read /home/Siebenschlaefer/.cpan/Metadata
>   Database was generated on Sat, 03 Nov 2001 19:12:15 GMT
> Test::Harness is up to date.

Strange. Perhaps one problem is that Test::Harness is a dual core/CPAN 
module; if you download it from CPAN, it'll install in site_perl by 
default, but since the core directories come first in @INC, it won't be 
seen unless you delete or rename the Harrness.pm in the core directory 
(or copy Harness.pm from site_perl into the core directory, overwriting 
the existing file).

I think Schwern said that Test::More has a dependency on a sufficiently 
new version of Test::Harness, but possibly the site_perl vs core dir 
thing caused the problem.

Cheers,
Philip
-- 
Philip Newton <[EMAIL PROTECTED]>

Reply via email to