Peter Prymmer <[EMAIL PROTECTED]> wrote on 03/06/2006 03:09:55 PM:
> that the kit failed two tests:
>
> lib/Net/Ping/t/510_ping_udp................................FAILED at
test 2
>
lib/Pod/Simple/t/corpustest................................FAILED--expected
43 tests, saw 2
I find that with my Multinet 5.1 stack that I can get the first
of these tests to pass both if I switch to icmp ping protocol and if I
set proc/priv=all. I cannot get it to pass with icmp and a NETMBX,TMPMBX
process.
The second test failure is due to an attempt to make vms illegal file
names in the test script (the filenames are illegal on ODS-2 - they could
be made legal on IDS-5 if appropriately escaped). A simple patch would be
to simply use:
--- bleed_at_27383/lib/Pod/Simple/t/corpustest.t 2006-03-05
18:48:27.163210000 -0500
+++ bleed/lib/Pod/Simple/t/corpustest.t 2006-03-07 23:39:30.054936000
-0500
@@ -122,7 +122,7 @@
next if $f =~ /nonesuch/;
- my $outfilename = ($HACK > 1) ? $wouldxml{$f} : "$wouldxml{$f}\.out";
+ my $outfilename = ($HACK > 1) ? $wouldxml{$f} : "$wouldxml{$f}_out";
if($HACK) {
open OUT, ">$outfilename" or die "Can't write-open $outfilename:
$!\n";
binmode(OUT);
end of possible patch
Unfortunately I have not tested that on a platform outside of VMS
(but I have a hard time seeing how it would do harm there).
I then reported a separate problem:
> and a patched copy of perl @ 27383 I see the same two test failures as
> well
> as the same inability for miniperl.exe to run installperl. A run of
> "mmk install" on the Alpha resulted in the same deep recursion message.
Sorry but I have made no progress on this problem. I am concerned.
Peter Prymmer
