Here's what I get with today's snapshot, building with Compaq C V6.4-005 on 
OpenVMS Alpha V7.2-1, -des configuration:

[.op]alarm..............................FAILED on test 4
[.op]glob...............................FAILED on test 8
[-.ext.encode.t]japanese................FAILED on test 18
[-.lib.extutils.t]installed.............FAILED on test 11
[-.lib.file.find.t]find.................FAILED on test 1
[-.lib.file.find.t]taint................FAILED on test 1
[-.lib.net.ping.t]110_icmp_inst.........FAILED on test 2
Failed 7/527 tests, 98.67% okay.

Details follow, mostly just reports rather than fixes at this point.

======
t/op/alarm.t

A sleep of 6 seconds in a subprocess takes 6 seconds even when there is a 
3-second alarm set in the parent; it appears that system() blocks alarm().  
So we probably have a bug/feature in our system() implementation that needs 
looking into.


======
t/op/glob.t

The test that is failing is:

# ... while ($var = glob(...)) should test definedness not truth

my $ok = "not ok 8\n";
$ok = "ok 8\n" while my $var = glob("0");
print $ok;


This test massively confuses me.  What is the meaning of the "0" in 
C<glob("0")>?  As far as I can see we are just testing for the existence of 
a file whose name matches the pattern "0" and failing if it does not exist.  
This is confirmed by the fact that if I create a file named "0" the test 
passes. Why would C<glob("0")> ever evaluate to true if there is no such 
file?  Why does the comment in the test say that C<while> "should test 
definedness not truth" but perlsyn says, "The C<while> statement executes 
the block as long as the expression is true"?  I'm sure I'm just being dumb
and this all makes perfect sense; someone please clue me in.

======
ext/Encode/t/Japanese.t

The underlying support is still a bit of a moving target so I'm not going to 
worry about this one yet, and I already posted details here:

<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2002-02/msg00398.html>


======
lib/ExtUtils/t/Installed.t

I haven't really begun to look at this one yet, but here are the detailed 
results.  I've snipped the ok's except where they serve to delimit the 
uninitialized value warnings.  


$ perl [-.lib.extutils.t]installed.t
1..43

Use of uninitialized value in concatenation (.) or string at 
[-.lib.extutils.t]installed.t line 54.
Use of uninitialized value in length at /perl_root/lib/ExtUtils/Installed.pm line 19.
Use of uninitialized value in string eq at /perl_root/lib/ExtUtils/Installed.pm line 
19.
Use of uninitialized value in concatenation (.) or string at 
[-.lib.extutils.t]installed.t line 54.
ok 9 - ... should find prog file under 

Use of uninitialized value in length at /perl_root/lib/ExtUtils/Installed.pm line 19.
Use of uninitialized value in string eq at /perl_root/lib/ExtUtils/Installed.pm line 
19.
not ok 11 - ... nor prog file outside path
#     Failed test ([-.lib.extutils.t]installed.t at line 63)
#          got: '1'
#     expected: '0'

Can't stat perl_root:[lib.site_perl.VMS_AXP]: no such file or directory
        ExtUtils::Installed::new('ExtUtils::Installed') called at 
[-.lib.extutils.t]installed.t line 82
ok 16 - The object isa ExtUtils::Installed

not ok 19 - new() should find modules with .packlists
#     Failed test ([-.lib.extutils.t]installed.t at line 125)
not ok 20 - The object isa ExtUtils::Packlist
#     Failed test ([-.lib.extutils.t]installed.t at line 126)
#     The object isn't defined
not ok 21 - ... should find version in modules
#     Failed test ([-.lib.extutils.t]installed.t at line 127)
#          got: undef
#     expected: '1.1.1'

Use of uninitialized value in length at /perl_root/lib/ExtUtils/Installed.pm line 19.
Use of uninitialized value in string eq at /perl_root/lib/ExtUtils/Installed.pm line 
19.
Use of uninitialized value in length at /perl_root/lib/ExtUtils/Installed.pm line 19.
Use of uninitialized value in string eq at /perl_root/lib/ExtUtils/Installed.pm line 
19.
ok 28 - ... should find no doc files given wrong dirs
Use of uninitialized value in length at /perl_root/lib/ExtUtils/Installed.pm line 19.
Use of uninitialized value in string eq at /perl_root/lib/ExtUtils/Installed.pm line 
19.
Use of uninitialized value in length at /perl_root/lib/ExtUtils/Installed.pm line 19.
Use of uninitialized value in string eq at /perl_root/lib/ExtUtils/Installed.pm line 
19.
not ok 29 - ... should find doc file in correct dir
#     Failed test ([-.lib.extutils.t]installed.t at line 171)
#          got: '2'
#     expected: '1'
not ok 30 - ... checking file name
#     Failed test ([-.lib.extutils.t]installed.t at line 172)
#                   'foobaz'
#     doesn't match '(?-xism:foobar$)'
ok 31 - ... should find all files with no type specified
Use of uninitialized value in length at /perl_root/lib/ExtUtils/Installed.pm line 19.
Use of uninitialized value in string eq at /perl_root/lib/ExtUtils/Installed.pm line 
19.
Use of uninitialized value in length at /perl_root/lib/ExtUtils/Installed.pm line 19.
Use of uninitialized value in string eq at /perl_root/lib/ExtUtils/Installed.pm line 
19.
# Looks like you failed 6 tests of 43.
%SYSTEM-F-ABORT, abort


======
lib/File/Find/t/find.t
lib/File/Find/t/taint.t

Hmm.  These fail when run with the entire test suite but not when run 
individually (with or without the test harness).  The failures crept in 
between 14471 and 14647.  That's all I know so far.


======
lib/Net/Ping/t/110_icmp_inst.t

This needs the additional patch located here:

<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2002-02/msg00111.html>



Reply via email to