On Wed, Oct 1, 2008 at 1:13 PM, Craig A. Berry <[EMAIL PROTECTED]> wrote: > On Tue, Sep 30, 2008 at 6:33 AM, Steve Hay <[EMAIL PROTECTED]> wrote: > >> Thanks, applied to bleadperl as 34446. >> >> Two local changes remain: >> >> Change 32357 by [EMAIL PROTECTED] on 2007/11/17 04:19:47 >> >> Skip Module::Build ppm test -- not ready for prime time on VMS. >> >> (ppm.t)
This is a great deal closer to working than it was, but still not quite there yet. >> Change 32351 by [EMAIL PROTECTED] on 2007/11/16 23:43:46 >> >> Silence ill-behaved or failing Module::Build tests on VMS. >> >> (test_type.t and xs.t parts only--the tilde.t part appears to have been >> superseded by code in 0.30. Please can you check that, Craig?) This was ok for now but we have more work to do upstream. I see these new failures after the integration of 0.30: lib/Module/Build/t/compat.....................................FAILED at test 13 lib/Module/Build/t/ext........................................FAILED at test 142 lib/Module/Build/t/tilde......................................FAILED at test 3 I think all of those were working last time I tried a CPAN version a few months ago but I obviously have not kept up on my testing. test_type.t and xs.t work fine individually but trigger a VMS-specific bug that causes the harness to see tests out of order. I think some output from a child process is bleeding through to the parent or something: $ perl test [-.lib.module.build.t]test_type.t lib/module/build/t/test_type....FAILED--expected test 5, saw test 4 Failed 1 test out of 1, 0.00% okay. [-.lib.module.build.t]test_type.t ### 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". u=6.56 s=0.00 cu=0.00 cs=0.00 scripts=1 tests=9 %SYSTEM-F-ABORT, abort $ perl test [-.lib.module.build.t]xs.t lib/module/build/t/xs....FAILED--expected test 12, saw test 11 Failed 1 test out of 1, 0.00% okay. [-.lib.module.build.t]xs.t ### 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". u=6.97 s=0.00 cu=0.00 cs=0.00 scripts=1 tests=23 %SYSTEM-F-ABORT, abort