At 3:30 PM -0500 3/13/08, Bill Norton wrote: >RX2600 OpenVMS V8.3 with current patches, HP C 7.2-022, on ODS5 disk with >hardlinks enabled. > >MMK test reported only one failure in 20_CPANPLUS-DIST-MM.T > >Running that individually doesn't add much information. >How do I find out more about the underlying error? >And, are the tests after number 30 actually failing but not fatally? > >$ @[.vms]test .EXE "" -"v" [-.lib.cpanplus.t]20_cpanplus-dist-mm.t
That is the authoritative way to get verbose test output, but if the test (as in this case) doesn't provide you with any useful comparison between what it got and what it expected, that method kind of falls flat. Here's what I do after a successful build to investigate a test failure further (adjust device and directory names for your local environment): $ set default [.perl] $ @perl_setup [now set PERL_ROOT to build directory, not install directory] $ define/trans=conc perl_root d0:[craig.perl.] %DCL-I-SUPERSEDE, previous value of PERL_ROOT has been superseded $ set default [.t] $ perl -"MTestInit" -d [-.lib.cpanplus.t]20_cpanplus-dist-mm.t That will put you in the Perl debugger where you can step through the test script, examine variables, set breakpoints, etc. Or run without the -d flag to just see all the test output, unfiltered by the test suite. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
