Re: Test errors for 5.8.3

Tue, 06 Apr 2004 20:00:50 -0700

Craig A. Berry wrote:
At 9:14 PM -0400 4/4/04, John E. Malmberg wrote:

I just have built Perl 5.8.3 on OpenVMS Alpha 7.3-2.

When running the tests, the vmsish test failed.

lib/vmsish...........................FAILED at test 25

That was patched here:

http://public.activestate.com/cgi-bin/perlbrowse?patch=22223

Patch applied, and the Alpha tests restarted. They took 51 minutes on a 600 Mhz.

All tests pass now on Alpha.

The same build on OpenVMS VAX 7.3 failed 8 tests.

PYTHON> search build.log failed
t/op/pack............................FAILED at test 0


Hmm. That would be good to know about. What do you get from

$ @[.vms]test .exe "" -"v" [.op]pack.t 


$   If F$Mode() .nes. "INTERACTIVE" Then Define/Nolog PERL_SKIP_TTY_TEST 1
$   MCR Sys$Disk:[]Perl. "-I[-.lib]" TEST. "-"v"" "[.OP]PACK.T" "" ""
  Improperly handled condition, image exit forced.
        Signal arguments              Stack contents
        Number = 00000003                00000000
        Name   = 000004B4                00207785
                 0016C111                00000000
                 03C00000                00000007
                                         00000000
                                         00000008
                                         00000001
                                         022D2AEA
                                         00004080
                                         00000000
        Register dump
        R0 = FFFF7FFF  R1 = FFFFFFFF  R2 = 00000000  R3 = FFFF7FFF
        R4 = FFFFFFFF  R5 = 00008000  R6 = 00000001  R7 = 00000008
        R8 = 00000009  R9 = 00000043  R10= 00207784  R11= 00000001
        AP = 7FE9FDE0  FP = 7FE9FDA0  SP = 7FE9FE14  PC = 0016C111
        PSL= 03C00000
t/OP/PACK....FAILED at test 0
Failed 1 test script out of 0, 0.00% okay.

I guess I will need to do a debug build. That will probably take a while.

PYTHON> @local_root:[000000]build_gnv_perl.com/out=build.log
%DCL-E-OPENOUT, error opening _$1$DIA1:[000000].DAT; as output
-RMS-E-PRV, insufficient privilege or file protection violation

Maybe a little longer. Now why is configure trying to put a file there?

In trying to chase that down I get:

Your PGFLQUOTA of 100000 appears too small to build perl5. Now that looks interesting as the command file is supposed to allow that much.

I fix that and still can not find the error, so am now running the procedure with out the output going to a log file, and now the build is running, probably well into tomorrow.


t/op/stat............................FAILED at test 75
This could be timezone setting related.


lib/ExtUtils/t/basic.................FAILED at test 26
lib/ExtUtils/t/Constant..............FAILED at test 23



Dunno about these.  There could be directory depth issues in the
tests themselves.

I thought ODS-2 on OpenVMS 7.3 allows deep directories on VAX. Well we look at this after I get a debug build.

lib/Math/BigInt/t/bare_mbi...........FAILED at test 2600
lib/Math/BigInt/t/bigintpm...........FAILED at test 2600
lib/Math/BigInt/t/sub_mbi............FAILED at test 2600



I think the BigInt module uses doubles to store chunks of very large
integers.  It probably makes some assumption that blows up on the
very limited exponent range of D_FLOAT, which is still the default
for Perl floating point on VAX.  You could do a G_FLOAT build or hack
into the innards of BigInt enough to see what it needs.  The author
has been very helpful sorting out similar situations in the past.

Will look at that also. Looks like trying the G_FLOAT build for VAX might be the easiest thing to try.


lib/vmsish...........................FAILED at test 22


Any chance you haven't reset the clock since the daylight savings change?

Considering that the build started before the DST, and the tests probably did not finish until after DST, Yes.

But if perl is using different rules than the system is, this could be a problem at other sites.

At my former employer, the time change was delayed until the end of a shift. I hope this does not indicate a window where perl scripts could misbehave.


Failed 8 test scripts out of 760, 98.95% okay. 


This has been better in recent memory.  I don't have any vaxen and
not many (any?) people who do are in the habit of building
development releases on a regular basis and reporting or fixing the
failures that show up.

I will do what I can find time for. The VAX is idle and has nothing better to do, so after I get something working on Alpha, I copy it over the VAX.

Now I also have to figure out how to set the [EMAIL PROTECTED] address subscribed to this list to a nomail setting.

Now to start applying the BASH patches to the kit.

-John
[EMAIL PROTECTED]
Personal Opinion Only

Reply via email to