> 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
> appear as
> ../lib/warnings.t
> io/socketpair.t
Those paths are relative to the t/ directory, and that's what you'll need for
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 test.
>
> 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
outside 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 when it
started doing that, but if you give it exactly what's in the list of failed
tests it should still work.
________________________________________
Craig A. Berry
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
