Craig Berry wrote in reply to me:
!>lib/File/Spec/t/rel2abs2rel..........FAILED at test 4
!
!I think this one gets confused when the default directory
!contains a rooted logical that does not point to the
!top-level directory on the volume.
I can confirm that the test will pass under
"set def dka300:[devel.perl.58x.perl-5_8_1-rc2]"
and will fail under "set def dev:[perl.58x.perl-5_8_1-rc2]".
It seems to be the case that canonpath() has a
bug on VMS. I note that as part of our current
build instructions (its actually been there for quite
a while) we recommend the use of a rooted logical for
perlsrc (line 519 and onward in README.vms) but we do not
warn that a test will fail if they use that method.
You then wrote:
!>lib/Net/Ping/t/190_alarm.............FAILED at test 6
!>lib/Net/Ping/t/450_service...........FAILED at test 8
!
!Those are skipped for folks running TCP/IP services
!because there is no echo service by default and that's
!what Net::Ping is based on. With Multinet they run but
!fail because there is unixy file locking done on sockets.
Indeed, they both have error messages similar to:
$ perl lib/Net/Ping/t/190_alarm.t
1..6
# Running under perl version 5.008001 for VMS
# Current time local: Mon Jul 21 12:56:45 2003
# Current time GMT: Mon Jul 21 16:56:45 2003
# Using Test.pm version 1.24
ok 1
ok 2
ok 3
ok 4
ok 5
not ok 6
# Failed test 6 in lib/net/ping/t/190_alarm.t at line 52
# lib/net/ping/t/190_alarm.t line 52 is: ok $@ =~ /alarm works/ or die $@;
fcntl F_GETFL: invalid argument at lib/net/ping/t/190_alarm.t line 43
%SYSTEM-F-ABORT, abort
Does the $Config{'d_fcntl_can_lock'} variable have anything
to do with this behavior and might we skip the last of 190_alarm.t
and 450_service.t if it is C<undef> as in my build?
$ search config.sh fcntl_can
d_fcntl_can_lock='undef'
I note that d_fcntl_can_lock is even set on a perl
build Configure'ed on Unix.
Peter Prymmer
