On Wed, 4 Feb 2004, Steve Fink wrote:
On Feb-02, Andrew Dougherty wrote:[EMAIL PROTECTED] 19184 languages/perl6/t/rx/call test error 1 years
Keep this one open. The tests still fail.
How recently did you check? I committed a reimplementation of perl6 regexes about a week ago. The above test still failed, but only due to a parrot memory corruption bug, and I committed something else the next day that coincidentally sidestepped the bug on my machine.
It's probably a different bug than #19184, but here's what I just got for
cd languages/perl6 make test
(This is for perl5.00503, Solaris 8/SPARC, Sun Workshop compiler)
Failed Test Status Wstat Total Fail Failed List of failed
----------------------------------------------------------------------- --------
t/rx/basic.t 8 2048 8 8 100.00% 1-8
t/rx/call.t 2 512 2 2 100.00% 1-2
t/rx/special.t 2 512 2 2 100.00% 1-2
All of the test failures look basically like this:
t/rx/basic..........Read on closed filehandle <PASM> at P6C/TestCompiler.pm line 71.
Use of uninitialized value at ../../lib/Parrot/Test.pm line 87.
# Failed test (t/rx/basic.t at line 7)
# got: 'error:imcc:main: Error reading source file t/rx/basic_1.pasm.
Apparently, you need to run "make" before "make test", or else the "perl6-config" file doesn't get created, and it all falls apart from there. This points to a problem with the perl6 Makefile (a missing dependency).
Finally, is it just me, or do these tests take a long time for everyone?
Yeah, something's definitely slow, and I think it's the perl6 script. While I was tracking down the above, I ran the following (which gets run as part of the test setup):
perl perl6 t/builtins/array_2.p6 --imc
The first time I ran this, it took several seconds (felt like 30 sec. or so) to run, and if I run 'top' while running 'make test', I see perl taking a lot of load. (Actually, I think it's building Perl6grammar.pm the first time it's run--that's probably the really slow step. But even after this, it takes almost 2 sec. to run.)
P6C::Parser uses Parse::RecDescent, which in my experience has been less than zippy, so that may be part of the problem.
JEff
