At 12:37 PM -0500 9/8/07, John E. Malmberg wrote: >With my submitted patches in place, and with one tentative bugfix to stat() in >VMS.C, here is a status of where things are for me on VMS. > >As rsync://ftp.linux.activestate.com is stuck at 31806, I have not been able >to easily test patches after that point.
It's working again. I haven't been building with symlink support so I'm not seeing all the same failures you are, but here are a few comments in those few cases where I have gotten a little further in determining what's going on. >NPLUS-Internals-Utils.t > >New failure: >not ok 19 - Looks like a proper version ># Failed test ' Looks like a proper version' ># at [-.lib.cpanplus.t]00_cpanplus-internals-utils.t line 78. ># '5_10_0' ># doesn't match '(?-xism:\d.\d.\d)' > >My guess is that somewhere a directory named '5.10.0' was converted to >'5_10_0' and that this regex can not deal with that. It was because 10 doesn't match \d, and #31800 should've taken care of it. > [-.lib.Module.Build.t]basic.t > >This passes when run interactively. Lots of output not prefixed by # The Module::Build tests have three completely different failure signatures when run with t/TEST, t/harness, and individually. Not sure what all is involved, but one problem is that when a test dies, it doesn't clean up after itself, so the next test cleans up and emits a warning about having to clean up first. When t/TEST sees the warning, it gives up the ghost with "Unexpected output at test 0." > > [-.lib.Module.Build.t]ext.t > >This passes when run interactively. > > [-.lib.Module.Build.t]extend.t > >not ok 7 ># Failed test at [-.lib.module.build.t]extend.t line 55. > >Looking for a VMS directory as a subdirectory of a VMS directory, and the >directory delimiters are causing the test to fail. > > [-.lib.Module.Build.t]install.t > >Manifying [.blib.lib]simple.pm -> [.blib.libdoc]__simple.rno >Use of uninitialized value within @dirs in pattern match (m//) at >/PROJECT_ROOT/PERL-BLEAD/lib/Pod/Man.pm line 795. There is a bug in Pod::Man::devise_title where it is surprised when an array element beyond the end of the array is undefined. I have a band-aid in progress. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
