On Mon, Nov 18, 2002 at 07:20:11PM -0600, Craig A. Berry wrote:
> I haven't had a chance to dig into the test failures yet, but here's
> where things are with a just-downloaded snapshot. Hopefully more later.
Please include your Descrip.mms with your reports. I can usually figure
things out better from that.
Latest snapshot has taken into account the VMS newline problem and failing
tests will show the generated oneliner to make it easier to figure out what
happened.
> Michael G Schwern wrote:
>
> >Look at MM_VMS->perl_oneliner() in the makemaker.org snapshot, let me know
> >if it'll work. If not, patch. It doesn't use any special ASCII escape
> >codes just s{"}{""}g;
>
>
> $ mmk test
> MCR perl_root:[000000]perl.exe
> "-ID0:[CRAIG.EXTUTILS-MAKEMAKER-SNAP.lib]" "-MExtUtils::Command::MM"
> "-e" "test_harness(0, '[.blib.li
> b]', '[.blib.arch]')" t/*.t
> t/00setup_dummy.........
> ok
> t/backwards.............
> ok
> t/basic.................
> %MMK-F-ERRUPD, error status %X0000002C occurred when updating target DISTDIR
> # Failed test (t/basic.t at line 138)
> # got: '1024'
> # expected: '0'
> # MCR perl_root:[000000]perl.exe -e "use File::Path; @dirs =
> map(VMS::Filespec::unixify($_),@ARGV); rmtree(\@dirs,0,0)" Big-Dummy-0.
> 01
This indicates you're behind or I did something wrong. That's the old RM_RF
target. It was replaced a couple days ago with one that just calls
ExtUtils::Command::rm_rf.
> # MCR perl_root:[000000]perl.exe
> "-MExtUtils::Manifest=manicopy,maniread" -e
> "manicopy(maniread(),'Big-Dummy-0.01', 'best');"
> # mkdir Big-Dummy-0.01
> # mkdir Big-Dummy-0.01: invalid argument at
> /BFD_TEST_ROOT/blib/lib/ExtUtils/Manifest.pm line 245
Hmm. That line in ExtUtils::Manifest just calls File::Path::mkpath. There
hasn't been a significant change to ExtUtils::Manifest in months, so it has
to be the point where its called... except the generation of the distdir
target hasn't changed in months either. Is it File::Path?
> t/perl_oneliner.........
> # Failed test (t/perl_oneliner.t at line 36)
> # got: 'foo'o bar"ar
> # '
> # expected: 'foo'o bar"ar'
> # Failed test (t/perl_oneliner.t at line 39)
> # got: 'foo
> # '
> # expected: 'foo'
That's just the "I'm going to helpfully add on the newline you obviously
forgot" problem with perl -e calls on VMS.
> syntax error at -e line 1, at EOF
> Execution of -e aborted due to compilation errors.
> %SYSTEM-F-ABORT, abort
> # Failed test (t/perl_oneliner.t at line 45)
> # got: '%SYSTEM-F-ABORT, abort
> # '
> # expected: 'foobar'
I guess my newline quoting isn't working.
# Escape newlines.
$cmd =~ s{\n}{-\n}g;
> Failed Test Stat Wstat Total Fail Failed List of Failed
> -------------------------------------------------------------------------------
> t/basic.t 44 1024 30 1 3.33% 27
> t/perl_oneliner.t 44 1024 7 3 42.86% 4-5 7
That's better than I expected. :)
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
<purl> Hey Schwern! honk, honk, honk, honk, honk, honk, honk, honk,
honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk,
honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk,
honk, honk, honk, honk, honk, honk, honk, honk, honk, honk, honk,
honk, honk, honk, honk, honk, honk, honk, honk, honk, honk!
