At 6:46 PM -0400 9/22/01, Michael G Schwern wrote:
>On Sat, Sep 22, 2001 at 01:17:18PM -0500, Craig A. Berry wrote:
> > Most of these will be difficult or impossible to debug without
>> access to a VMS system.
>
>Oh ye of little faith. Give me the verbose output of each, please.
Will do.
>There should be a good deal of diagnostic info in there.
Sometimes yes, sometimes not.
> > manifest.t and chdir.t assume case-preserving file systems.
>
>"assume case-preserving file systems"... buh.
>
>Ok, trying to wrap my brane around that... what does that mean? Could
>open(FILE, ">Elite"); create file called 'eLiTe'?
It creates a file called ELITE.T, regardless of whether you give it
upper, lower, or mixed case. When you get it back from the C
library, however (say from readdir()), it will be in all lower case
in a vague attempt to make it look Unix-like. It appears, though,
that Cwd::getcwd() does not follow this convention since it gives its
results in upper case:
$ perl -"MCwd" -e "chdir('test'); print Cwd::getcwd();"
D0:[CRAIG.TEST]
>For chdir.t, that might be fixed by #12124.
I'll take a look. In the meantime, here's the verbose output:
$ perl [.op]chdir.t
1..24
not ok 1 - chdir("t")
# Failed test ([.op]chdir.t at line 22)
not ok 2 - abs_path() agrees
# Failed test ([.op]chdir.t at line 23)
# got: 'USER1:[SCHWERN.PERL.T]'
# expected: 'USER1:[SCHWERN.PERL.T.t]'
ok 3 - chdir() w/$ENV{HOME} set
not ok 4 - abs_path() agrees
# Failed test ([.op]chdir.t at line 45)
# got: 'USER1:[SCHWERN.PERL.T.OP]'
# expected: 'USER1:[SCHWERN.PERL.T.op]'
ok 5 - and back again
not ok 6 - chdir(undef) w/$ENV{HOME} set
# Failed test ([.op]chdir.t at line 51)
not ok 7 - abs_path() agrees
# Failed test ([.op]chdir.t at line 52)
# got: 'USER1:[SCHWERN]'
# expected: 'USER1:[SCHWERN.PERL.T]'
not ok 8 - chdir('') w/$ENV{HOME} set
# Failed test ([.op]chdir.t at line 55)
not ok 9 - abs_path() agrees
# Failed test ([.op]chdir.t at line 56)
# got: 'USER1:[SCHWERN]'
# expected: 'USER1:[SCHWERN.PERL.T]'
ok 10 - chdir() w/$ENV{LOGDIR} set
not ok 11 - abs_path() agrees
# Failed test ([.op]chdir.t at line 45)
# got: 'USER1:[SCHWERN]'
# expected: 'USER1:[SCHWERN.PERL.T.op]'
ok 12 - and back again
not ok 13 - chdir(undef) w/$ENV{LOGDIR} set
# Failed test ([.op]chdir.t at line 51)
not ok 14 - abs_path() agrees
# Failed test ([.op]chdir.t at line 52)
# got: 'USER1:[SCHWERN]'
# expected: 'USER1:[SCHWERN.PERL.T]'
not ok 15 - chdir('') w/$ENV{LOGDIR} set
# Failed test ([.op]chdir.t at line 55)
not ok 16 - abs_path() agrees
# Failed test ([.op]chdir.t at line 56)
# got: 'USER1:[SCHWERN]'
# expected: 'USER1:[SCHWERN.PERL.T]'
ok 17 - chdir() w/$ENV{SYS$LOGIN} set
not ok 18 - abs_path() agrees
# Failed test ([.op]chdir.t at line 45)
# got: 'USER1:[SCHWERN.PERL.T.OP]'
# expected: 'USER1:[SCHWERN.PERL.T.op]'
ok 19 - and back again
not ok 20 - chdir(undef) w/$ENV{SYS$LOGIN} set
# Failed test ([.op]chdir.t at line 51)
not ok 21 - abs_path() agrees
# Failed test ([.op]chdir.t at line 52)
# got: 'USER1:[SCHWERN.PERL.T.OP]'
# expected: 'USER1:[SCHWERN.PERL.T]'
not ok 22 - chdir('') w/$ENV{SYS$LOGIN} set
# Failed test ([.op]chdir.t at line 55)
not ok 23 - abs_path() agrees
# Failed test ([.op]chdir.t at line 56)
# got: 'USER1:[SCHWERN.PERL.T.OP]'
# expected: 'USER1:[SCHWERN.PERL.T]'
ok 24 - chdir() w/o any ENV set
not ok 25 - abs_path() agrees
# Failed test ([.op]chdir.t at line 67)
# got: 'USER1:[SCHWERN.PERL.T.OP]'
# expected: 'USER1:[SCHWERN.PERL.T]'
# Looks like you planned 24 tests but ran 1 extra.
%SYSTEM-F-ABORT, abort
>manifest.t... we can probably fix it if I can see the test output.
$ perl [-.lib.extutils]manifest.t
1..31
ok 1 - use ExtUtils::Manifest;
ok 2 - make mantest directory
ok 3 - chdir() to mantest
ok 4 - add a temporary file
not ok 5 - mkmanifest() displayed it's additions
# Failed test ([-.lib.extutils]manifest.t at line 58)
# got: 'Added to MANIFEST: MANIFEST
Added to MANIFEST: foo
Added to MANIFEST: manifest
'
# expected: 'Added to MANIFEST: MANIFEST
Added to MANIFEST: foo
'
ok 6 - create MANIFEST file
not ok 7 - check files in MANIFEST
# Failed test ([-.lib.extutils]manifest.t at line 67)
# got: '3'
# expected: '2'
ok 8 - no additional files in directory
ok 9 - add another file
ok 10 - MANIFEST now out of sync
ok 11 - warning that bar has been added
ok 12 - bar reported as new
ok 13 - disabled warnings
not ok 14 - got skipping warning
# Failed test ([-.lib.extutils]manifest.t at line 91)
# 'Skipping manifest.skip
'
# doesn't match '(?-xism:^Skipping MANIFEST\.SKIP)'
ok 15 - no output here
ok 16 - listed skipped files
ok 17 - listing skipped with filecheck()
ok 18 - created moretest directory
not ok 19 - manifind found [.moretest]quux
# Failed test ([-.lib.extutils]manifest.t at line 109)
ok 20 - two files found
not ok 21 - both files found
# Failed test ([-.lib.extutils]manifest.t at line 114)
# got: 'foo manifest'
# expected: 'MANIFEST foo'
not ok 22 - maniread found comment
# Failed test ([-.lib.extutils]manifest.t at line 118)
# got: 'none #none'
# expected: '#none'
ok 23 - made copy directory
not ok 24 - warned about MANIFEST.SKIP
# Failed test ([-.lib.extutils]manifest.t at line 131)
# got: 'Skipping manifest.skip'
# expected: 'Skipping MANIFEST.SKIP'
ok 25 - carped about none
ok 26 - using a new manifest file
ok 27 - remove all added files
ok 28 - remove moretest directory
ok 29 - remove copy directory
ok 30 - return to parent directory
not ok 31 - remove mantest directory
# Failed test ([-.lib.extutils]manifest.t at line 40)
# Looks like you failed 8 tests of 31.
%SYSTEM-F-ABORT, abort
> > kill_perl.t runs fine by itself but not in the test suite.
>
>Run vms/test.com on kill_perl.t with the -v flag set and show me the
>verbose output.
Runs fine by itself, either directly from perl or from within test.com.
>Did t/op/misc.t used to fail? If so, then it has something to do with
>the test names on the end confusing test.com.
Don't remember offhand about misc.t, but it is almost surely
something in test.com since it only happens when the entire test
suite is run.
>Ok, taint.t. The problem is either inside tainted() or a problem with
>how it's picking it's value. I don't think the problem is that %ENV
>is not tainted.
Maybe, maybe not. There is a good deal of special handling of both
%ENV and tainting in vms/vms.c. We could have a genuine bug there,
or it may just be test bugs. I'll post the taint test failures in a
separate message.
>lib/Test/Simple/t/todo.t failing is probably just a minor bug in
>vms/test.com
That may be an issue, but the failures I've noticed are independent of test.com:
$ perl [-.lib.test.simple.t]todo.t
1..13
not ok 1 - Expected failure # TODO Just testing the todo interface.
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 18)
not ok 2 - Another expected failure # TODO Just testing the todo interface.
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 19)
ok 3 - This is not todo
not ok 4 - Yet another failure # TODO Just testing the todo interface.
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 29)
ok 5 - This is still not todo
not ok 6 - ok # TODO testing that error messages don't leak out of todo
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 38)
not ok 7 - like # TODO testing that error messages don't leak out of todo
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 40)
# 'this'
# doesn't match '/that/'
not ok 8 - is # TODO testing that error messages don't leak out of todo
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 41)
# got: 'this'
# expected: 'that'
not ok 9 - isnt # TODO testing that error messages don't leak out of todo
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 42)
# it should not be 'this'
# but it is.
not ok 10 - Fooble->can(yarble) # TODO testing that error messages don't leak out of
todo
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 44)
# Fooble->can('yarble') failed
not ok 11 - object->isa('yarble') # TODO testing that error messages don't leak out of
todo
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 45)
# The object isn't a reference
not ok 12 - use Fooble; # TODO testing that error messages don't leak out of todo
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 46)
# Tried to use 'Fooble'.
# Error: Can't locate Fooble.pm in @INC (@INC contains:
perl_root:[lib.VMS_AXP.5_7_2] perl_root:[lib] perl_root:[lib.site_perl.
VMS_AXP] perl_root:[lib.site_perl] /perl_root/lib/site_perl .) at (eval 2) line 2.
not ok 13 - require Fooble; # TODO testing that error messages don't leak out of todo
# Failed (TODO) test ([-.lib.test.simple.t]todo.t at line 47)
# Tried to require 'Fooble'.
# Error: Can't locate Fooble.pm in @INC (@INC contains:
perl_root:[lib.VMS_AXP.5_7_2] perl_root:[lib] perl_root:[lib.site_perl.
VMS_AXP] perl_root:[lib.site_perl] /perl_root/lib/site_perl .) at (eval 3) line 2.
>PS Could you please, please, please, take a swing at getting Perl
>installed on the OpenVMS Compaq testdrive account?
Done. I'll try to post more details in the next day or two. For now
you can run it by logging in and typing the following commands:
$ sd [.perl]
$ @perl_setup
$ define/translation=concealed perl_root user1:[schwern.perl.]
I've also installed a vi-like editor which you can get by typing
"vile"; GNU diff is available as "gdiff" and GNU patch is available
as "gpatch".
--
____________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
"Literary critics usually know what they're
talking about. Even if they're wrong."
-- Perl creator Larry Wall
