Re: Experience installing on Alpha VMS 8.3
"Miller, Edward S." via vmsperl <[email protected]> Fri, 19 Feb 2021 23:17:28 +0000
| Newsgroups | gmane.comp.lang.perl.ports.vms |
|---|---|
| Message-ID | <BY5PR07MB698248336D1D31B4D38D63BDFF849@BY5PR07MB6982.namprd07.prod.outlook.com> |
--_000_BY5PR07MB698248336D1D31B4D38D63BDFF849BY5PR07MB6982namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
As I stated presviously in this thread, our PERL installation (Alpha VMS 8.=
3) was apparently successful
and I had my previous questions answered, thank you.
I have an additional question, which is mostly academic so it's fine if I d=
on't get an answer.
Also I have some observations/suggestions related to the test procedures.
My question: if I were to do a new install on another VMS system, could I =
skip the MMK TEST step?
Does this step do anything that is a prerequisite for the final MMK INSTALL=
step? Does this step ever
fail in such a way as to make the INSTALL step impossible?
Some observations about the test procedures.
At the end of the MMK TEST job the following message appears:
### Since not all tests were successful, you may want to run some of
### them individually and examine any diagnostic messages they produce.
### See the INSTALL document's section on "make test".
### You have a good chance to get more information by running
### ./perl harness
### in the 't' directory since most (>=3D80%) of the tests succeeded.
I have performed both of these operations. The recommendation to run the H=
ARNESS test is not
mentioned in the README.VMS file. I'd suggest some mention in README.VMS a=
bout HARNESS and the
motivation for running it as well (in addition to MMK TEST). My IMPRESSION=
is that the information
these tests provide is not likely to be actionable by the unknowledgable bl=
oke who is just trying to
install PERL to satisfy a user request.
My experience running HARNESS:
It reported 64 failed tests (where MMK TEST reported 58). Most were the=
same, but 8
failures were unique to HARNESS, 2 were unique to MMK TEST.
Tests which fail with MMK_TEST but not HARNESS:
io/socketpair.t (explicitly skipped by the HARNESS job)
op/lexsub.t (not mentioned by the HARNESS job)
Tests which fail with HARNESS but not MMK_TEST:
../lib/File/Copy.t
../lib/diagnostics.t
io/data.t
op/gv.t
op/lex.t
op/sigdispatch.t
run/switchC.t
run/switchx.t
(None of the above HARNESS failures were mentioned as being tes=
ted in the MMK_TEST job.)
I ran the 8 tests uniquely reported as failed by HARNESS thru the proced=
ure
$ @[.vms]test .EXE "" -"v" <testname>
That procedure found NO failures in any of those failed HARNESS tests.
It appears that failure is in the eye of the beholder.
Thanks,
Ed Miller SLAC NAL
________________________________
From: Craig Berry <[email protected]>
Sent: Tuesday, February 16, 2021 6:38 AM
To: Miller, Edward S. <[email protected]>; [email protected] <vmsperl@pe=
rl.org>
Subject: Re: Experience installing on Alpha VMS 8.3
> On Feb 15, 2021, at 10:47 PM, Miller, Edward S. via vmsperl <vmsperl@perl=
.org> wrote:
>
> During the run of all tests these two examples appear as
> lib/warnings ................................................... FAILED=
at test 710
> t/io/socketpair ................................................ FAILED=
--unexpected output at test 0
Those paths are relative to the top-level directory.
> In the list of all failed tests at the end of the run of all tests they a=
ppear as
> ../lib/warnings.t
> io/socketpair.t
Those paths are relative to the t/ directory, and that's what you'll need f=
or running tests individually.
> The command
> $ @[.vms]test .EXE "" -"v" [.io]socketpair.t
> reruns that test with more detailed output. Using similar syntax for all=
failing tests that are reported
> with names specified as "t/..." also reruns the corresponding failing te=
st.
>
> I didn't find the proper command to rerun the test on the warnings.t file=
(or any of the other test names that did
> not match the "t/..." syntax).
This oughta do it:
$ @[.vms]test .exe -"v" "../lib/warnings.t"
Apparently using VMS syntax filenames no longer works when running tests ou=
tside of the t/ hierarchy, so if you gave it this:
$ @[.vms]test .exe -"v" [-.lib]warnings.t
it would try to run the mongrel filename t/[-.lib]warnings.t. Not sure whe=
n it started doing that, but if you give it exactly what's in the list of f=
ailed tests it should still work.
________________________________________
Craig A. Berry
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
--_000_BY5PR07MB698248336D1D31B4D38D63BDFF849BY5PR07MB6982namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
As I stated presviously in this thread, our PERL installation (Alpha VMS 8.=
3) was apparently successful
<div>and I had my previous questions answered, thank you.</div>
<div>I have an additional question, which is mostly academic so it's fine i=
f I don't get an answer.</div>
<div>Also I have some observations/suggestions related to the test procedur=
es.</div>
<div><br>
</div>
<div>My question: if I were to do a new install on another VMS system=
, could I skip the MMK TEST step?</div>
<div>Does this step do anything that is a prerequisite for the final MMK IN=
STALL step? Does this step ever</div>
<div>fail in such a way as to make the INSTALL step impossible?</div>
<div><br>
</div>
<div>Some observations about the test procedures.</div>
<div><br>
</div>
<div>At the end of the MMK TEST job the following message appears:</div>
<div> ### Since not all tests were successful, you may want to=
run some of</div>
<div> ### them individually and examine any diagnostic message=
s they produce.</div>
<div> ### See the INSTALL document's section on "make tes=
t".</div>
<div> ### You have a good chance to get more information by ru=
nning</div>
<div> ### ./perl harness</div>
<div> ### in the 't' directory since most (>=3D80%) of the =
tests succeeded.</div>
<div><br>
</div>
<div>I have performed both of these operations. The recommendation to=
run the HARNESS test is not</div>
<div>mentioned in the README.VMS file. I'd suggest some mention in RE=
ADME.VMS about HARNESS and the</div>
<div>motivation for running it as well (in addition to MMK TEST). My =
IMPRESSION is that the information</div>
<div>these tests provide is not likely to be actionable by the unknowledgab=
le bloke who is just trying to</div>
<div>install PERL to satisfy a user request.</div>
<div><br>
</div>
<div>My experience running HARNESS:</div>
<div> It reported 64 failed tests (where MMK TEST reported 58).=
Most were the same, but 8</div>
<div> failures were unique to HARNESS, 2 were unique to MMK TES=
T.</div>
<div><br>
</div>
<div> Tests which fail with MMK_TEST but =
not HARNESS:</div>
<div> io/socketpair.t (expli=
citly skipped by the HARNESS job)</div>
<div> op/lexsub.t &n=
bsp;(not mentioned by the HARNESS job)</div>
<div><br>
</div>
<div> Tests which fail with HARNESS but n=
ot MMK_TEST:</div>
<div> ../lib/File/Copy.t</div>
<div> ../lib/diagnostics.t</div>
<div> io/data.t</div>
<div> op/gv.t</div>
<div> op/lex.t</div>
<div> op/sigdispatch.t</div>
<div> run/switchC.t</div>
<div> run/switchx.t</div>
<div> (None of the above HARNESS f=
ailures were mentioned as being tested in the MMK_TEST job.)</div>
<div><br>
</div>
<div> I ran the 8 tests uniquely reported as failed by HARNESS =
thru the procedure</div>
<div> $ @[.vms]test .EXE &qu=
ot;" -"v" <testname></div>
<div><br>
</div>
<div> That procedure found NO failures in any of those failed H=
ARNESS tests.</div>
<div> It appears that failure is in the eye of the beholder.</d=
iv>
<div><br>
</div>
<div>Thanks,</div>
<div> Ed Miller SLAC NAL</div>
<br>
</div>
<div id=3D"appendonsend"></div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Craig Berry <craig=
[email protected]><br>
<b>Sent:</b> Tuesday, February 16, 2021 6:38 AM<br>
<b>To:</b> Miller, Edward S. <[email protected]>; [email protected]=
g <[email protected]><br>
<b>Subject:</b> Re: Experience installing on Alpha VMS 8.3</font>
<div> </div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText"><br>
<br>
> On Feb 15, 2021, at 10:47 PM, Miller, Edward S. via vmsperl <vmsper=
[email protected]> wrote:<br>
> <br>
> During the run of all tests these two examples appear as<br>
> lib/warnings .............................................=
...... FAILED at test 710<br>
> t/io/socketpair ..........................................=
...... FAILED--unexpected output at test 0<br>
<br>
Those paths are relative to the top-level directory.<br>
<br>
> In the list of all failed tests at the end of the run of all tests the=
y appear as<br>
> ../lib/warnings.t<br>
> io/socketpair.t<br>
<br>
Those paths are relative to the t/ directory, and that's what you'll need f=
or running tests individually.<br>
<br>
> The command<br>
> $ @[.vms]test .EXE "" -"v" [.io]=
socketpair.t<br>
> reruns that test with more detailed output. Using similar syntax=
for all failing tests that are reported<br>
> with names specified as "t/..." also reruns the corres=
ponding failing test.<br>
> <br>
> I didn't find the proper command to rerun the test on the warnings.t f=
ile (or any of the other test names that did<br>
> not match the "t/..." syntax).<br>
<br>
This oughta do it:<br>
<br>
$ @[.vms]test .exe -"v" "../lib/warnings.t"<br>
<br>
Apparently using VMS syntax filenames no longer works when running tests ou=
tside of the t/ hierarchy, so if you gave it this:<br>
<br>
$ @[.vms]test .exe -"v" [-.lib]warnings.t<br>
<br>
it would try to run the mongrel filename t/[-.lib]warnings.t. Not sur=
e when it started doing that, but if you give it exactly what's in the list=
of failed tests it should still work.<br>
<br>
________________________________________<br>
Craig A. Berry<br>
<br>
"... getting out of a sonnet is much more<br>
difficult than getting in."<br>
&nb=
sp; Brad Leithauser<br>
<br>
</div>
</span></font></div>
</body>
</html>
--_000_BY5PR07MB698248336D1D31B4D38D63BDFF849BY5PR07MB6982namp_--