Re: Experience installing on Alpha VMS 8.3
"Miller, Edward S." via vmsperl <[email protected]> Tue, 16 Feb 2021 20:10:49 +0000
| Newsgroups | gmane.comp.lang.perl.ports.vms |
|---|---|
| Message-ID | <BY5PR07MB69820671D200567D9FCCA37BFF879@BY5PR07MB6982.namprd07.prod.outlook.com> |
--_000_BY5PR07MB69820671D200567D9FCCA37BFF879BY5PR07MB6982namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Craig, Thanks. I've now re-run all of the 58 failed tests using the appropriate s= yntax. The results aren't particularly meaningful to me, and I'm assuming no one e= lse is likely to want to see them. Perhaps this syntax could be clarified in the README.VMS file (for the bene= fit of those who are only minimally conversant with unix file name syntax). Thanks for all your help. -- Ed ________________________________ 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_BY5PR07MB69820671D200567D9FCCA37BFF879BY5PR07MB6982namp_ 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);"> Hi Craig,</div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> </div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> Thanks. I've now re-run all <span style=3D"color: rgb(0, 0, 0); = font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">of th= e 58 failed tests using the appropriate syntax.</span></div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> The results aren't particularly meaningful to me, and I'm assuming no one e= lse is likely to want to see them.</div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> Perhaps this syntax could be clarified in the README.VMS file (for the bene= fit of those who are only minimally</div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> conversant with unix file name syntax).</div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> </div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> Thanks for all your help.</div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> </div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> -- Ed</div> <div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size= : 12pt; color: rgb(0, 0, 0);"> <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_BY5PR07MB69820671D200567D9FCCA37BFF879BY5PR07MB6982namp_--