At 8:42 PM +0200 10/19/03, Willem Grooters wrote:
>I just downloaded the latest perl set for VMS
It's always best to report the exact Perl version
$ perl -v
or with additional configuration info available from
$ perl -"V"
>However, running tests (MMS TEST) I got errors:
>
>t/io/fs FAILED on test 33
>t/op/stat FAILED on test 29
>lib/extutils/t/constant FAILED on test 3
>
>I found out to execute:
>
>$ perl [.t.io]fs.t
>
>which gave me the full list, and a failure on RENAME (test 33) and -d
>(remove??) of tmp.dir (34).
>After I edited the script stating 'set file tmp.dir /protection=o:d'
>to set file tmp.dir/protection=(s:rwed,o:rwed) these tests went Ok. (I ran
>them as SYSTEM...)
>
>$ perl [.t.op]stat.t
>
>gave me test 29 again, and line 203 in error.
>That's this line:
>
>ok(-o $tmpfile, '-o');
>
>is the "owned by" - in my case: SYSTEM, that failes?
>Again, this _could_ be a problem when running as SYSTEM. But I doubt it.
The test suite temporarily downgrades privs, so it's conceivable that
if the files are owned by someone other than SYSTEM, then even SYSTEM
wouldn't have access. However, the fact that you can reproduce the
problem running the tests individually suggests that this explanation
isn't helpful (unless you also happen to run your SYSTEM account with
some of its default privs downgraded). Check who owns the temp files
in question and (since these are temp files created on the fly) check
for any non-default ownership inheritance possibilities.
>The last:
>
>perl [.lib.extutils.t]constant.t
>
>went wrong id MAKE AL, since:
>
># perl=DKB100:[user.WILLEM.perl.PERL-5_8_1]PERL.EXE;1
># ext-538968653 being created...
>1..272
># Simple tests
># ext-538968653/0 being created...
>ok 1
>ok 2
># make = 'MMS all'
>%MMS-F-GWKNOACTS, Actions to update EXTTEST.C are unknown.
>not ok 3 # MMS all failed: 1024
># cp exttest.pm [---.lib]exttest.pm
># MCR [---]miniperl.exe "-I[---.lib]" "-I[---.lib]" -e "use
>ExtUtils::Mksymlists
>;" -e "Mksymlists('NAME' => 'ExtTest', 'DL_FUNCS' => { }, 'DL_VARS' =>
>[],
> 'FUNCLIST' => [])"
># MCR [---]miniperl.exe -e "print
>""[---.lib.auto.ExtTest]ExtTest.olb/Include=Ex
>tTest\n[---.lib.auto.ExtTest]ExtTest.olb/Library\n"";" >>EXTTEST.OPT
># MCR [---]miniperl.exe -e "print qq{[---]PerlShr.exe/Share\n}"
>>>EXTTEST.OPT
># Copy/NoConfirm EXTTEST.OPT [---.LIB.AUTO.EXTTEST]EXTTEST.OPT
># %MMS-F-GWKNOACTS, Actions to update EXTTEST.C are unknown.
># ext-538968653 being removed...
>%SYSTEM-W-PLHLDR, reserved for future use
>$
>
>I guess the MMS-file (descrip.mms) isn't Ok here? But where can I find it?
It gets cleaned up either later in constant.t or by subsequent tests;
it's the extension-building parts of Perl that are being explicitly
tested here, so a fake extension is created and built. I would start
by trying to reproduce your problem with MMK. If you are running on
an ODS-5 disk, I would also try to reproduce the problem on ODS-2
(MMS has trouble applying default rules in a mixed-case environment).
--
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
