On Sep 2, 2010, at 9:17 AM, Vorländer, Martin wrote:
MMK test yields "Failed 25 tests out of 1625, 98.46% okay." with
CPANplus, ExtUtils::MakeMaker, and Module::Build, and
ExtUtils::Install
contributing 21 of the failed tests. I include the results of
running
the other 4 in this mail.
I don't actually see the test output.
I had appended it in an attachment.
Doh! Don't know how I missed that.
Here goes...
I'm at a loss what to do with respect to the perl5db.t test failure.
Well, the place to start is here:
$ sea [.lib]perl5db.pl "must not source"/win=5
unless ( is_safe_file($file) ) {
CORE::warn <<EO_GRIPE;
perldb: Must not source insecure rcfile $file.
You or the superuser must be the owner, and it must not
be writable by anyone but its owner.
The stat.t failure also has something to do with ownership. Not sure
what exactly, but anything out of the ordinary involving ACLs, default
permissions, files created under one account and accessed under
another, etc., might be worth checking.
$ @ [.VMS]TEST .EXE "" -"v" [-.op]stat.t
# Failed at [.op]stat.t line 218
1..107
ok 1 # skip No link count - Hard link support not built in.
ok 2 - mtime
ok 3 - mtime == ctime
ok 4 # skip link() unimplemented
ok 5 # skip link() unimplemented
ok 6 # skip link() unimplemented
ok 7 # skip link() unimplemented
ok 8 # skip link() unimplemented
ok 9 # skip link() unimplemented
ok 10 - -z on empty filehandle
ok 11 - and -s
ok 12 - -z on empty file
ok 13 - and -s
ok 14 - -z on empty filehandle
ok 15 - and -s
ok 16 - -z on non-empty file
ok 17 - and -s
ok 18 - chmod 0000
ok 19 # skip -r, -w and -x have different meanings on VMS
ok 20 # skip -r, -w and -x have different meanings on VMS
ok 21 # skip -r, -w and -x have different meanings on VMS
ok 22 - chmod 0700
ok 23 - -r
ok 24 - -w
ok 25 - -x
ok 26 - -f
ok 27 - !-d
ok 28 - -d cwd
ok 29 - !-f cwd
ok 30 - symlink() implemented
ok 31 - symlink() ok
ok 32 - -l
not ok 33 - -o
t/[.OP]STAT....FAILED at test 33
$ @ [.VMS]TEST .EXE "" -"v" [-.lib]perl5db.t
1..8
perldb: Must not source insecure rcfile ./.perldb.
Loading DB routines from perl5db.pl version 1.33
Editor support available.
Enter h or `h h' for help, or `perldoc perldebug' for more help.
main::(../lib/perl5db/t/eval-line-bug:6):
6: my $i = 5;
DB<1> c
Debugged program terminated. Use q to quit or R to restart,
use o inhibit_exit to avoid stopping after program termination,
h q, h R or h o to get additional info.
DB<1> q
t/[-.LIB]PERL5DB....FAILED--unexpected output at test 0
$ @ [.VMS]TEST .EXE "" -"v" [-.lib]vmsish.t
1..25
ok 1 # skip tests for non-VMS only
ok 2 - simple Perl invokation: POSIX success status
ok 3 - importing vmsish [vmsish status]
ok 4 - unimport vmsish [POSIX STATUS]
ok 5 - lex scope of vmsish [vmsish status]
ok 6 - outer lex scope of vmsish [POSIX status]
ok 7 - importing vmsish exit [POSIX status]
ok 8 - POSIX ERR exit, DCL error message check
ok 9 - vmsish status check, POSIX ERR exit
ok 10 - vmsish OK exit, DCL error message check
ok 11 - vmsish status check, vmsish OK exit
ok 12 - vmsish ERR exit, DCL error message check
ok 13 - vmsish ERR exit, vmsish status check
ok 14 - POSIX ERR exit, vmsish hushed, DCL error message check
ok 15 - vmsish ERR exit, vmsish hushed, DCL error message check
ok 16 - vmsish ERR exit, no vmsish hushed, DCL error message check
ok 17 - die, vmsish hushed, DCL error message check
ok 18 - croak, vmsish hushed, DCL error message check
ok 19 - vmsish ERR exit, vmsish hushed at runtime, DCL error message
check
# Failed at [-.lib]vmsish.t line 151
# Failed at [-.lib]vmsish.t line 157
# Failed at [-.lib]vmsish.t line 164
# Failed at [-.lib]vmsish.t line 167
ok 20 - compile ERR exit, vmsish hushed, DCL error message check
ok 21 - use vmsish qw(time)
not ok 22 - (time) UTC: 1283420026 VMS: 1283420026
t/[-.LIB]VMSISH....FAILED at test 22
________________________________________
Craig A. Berry
mailto:craigbe...@mac.com
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
