Hundreds of errors?
Andy Dougherty
actually think it's in PGE, just that the new PGE is triggering some other
bugs elsewhere in parrot (that have been showing up in t/library/dumper.t
recently). I don't recall such problems in parrot-0.4.2. I didn't test
parrot-0.4.3.
The first sign of trouble is during the build process:
../../parrot pgc.pir --output=PGE/builtins_gen.pir PGE/builtins.pg
set_integer_keyed() not implemented in class 'Integer'
current instr.: 'parrot;PGE::P6Regex;parse_subrule' pc 7603 (compilers/pge/PGE/P6Regex.pir:619)
called from Sub 'parrot;PGE::OPTable;parse' pc 2024 (compilers/pge/PGE/OPTable.pir:572)
called from Sub 'parrot;PGE::Regex;regex' pc 5938 (compilers/pge/PGE/P6Regex.pir:145)
called from Sub 'parrot;PGE::P6Regex;compile_p6regex' pc 5797 (compilers/pge/PGE/P6Regex.pir:82)
called from Sub 'parrot;PGE::P6Grammar;__onload' pc 212 (pgc.pir:164)
called from Sub 'parrot;PGE::P6Grammar;main' pc 16 (pgc.pir:53)
Re-running make apparently succeeds, but then gets over 800 errors of
apparently similar form, mostly from library/dumper or else pge-related
tests. Sorting the different types of failures:
Occurrences Error message:
225 got: 'Null PMC access in set_integer_native()
213 got: 'set_pmc_keyed() not implemented in class 'Integer'
184 got: 'set_pmc_keyed() not implemented in class 'String'
116 got: 'set_integer_keyed() not implemented in class 'Integer'
78 got: 'set_string_keyed() not implemented in class 'Integer'
12 got: 'Cpu Limit Exceeded
8 got: '"array:" => Null PMC access in get_integer()
5 got: '"VAR1" => Null PMC access in get_integer()
4 got: '"array" => Null PMC access in get_integer()
2 got: '"strings" => Null PMC access in get_integer()
2 got: '"hash1" => Null PMC access in get_integer()
1 got: '"hash" => Null PMC access in get_integer()
1 got: '"array of various strings" => Null PMC access in get_integer()
1 got: '"VAR1" => PMC 'bar' __value => {
Here's another sample:
$ ./parrot t/library/dumper_1.pir
"array" => Null PMC access in get_integer()
current instr.: 'parrot;Data::Dumper::Base;newIndent' pc 199 (/home/doughera/src/parrot/parrot-andy/runtime/parrot/library/Data/Dumper/Base.pir:158)
called from Sub 'parrot;Data::Dumper::Default;genericArray' pc 370 (/home/doughera/src/parrot/parrot-andy/runtime/parrot/library/Data/Dumper/Default.pir:290)
called from Sub 'parrot;Data::Dumper::Base;dump' pc 393 (/home/doughera/src/parrot/parrot-andy/runtime/parrot/library/Data/Dumper/Base.pir:251)
called from Sub 'parrot;Data::Dumper::Default;dumpWithName' pc 39 (/home/doughera/src/parrot/parrot-andy/runtime/parrot/library/Data/Dumper/Default.pir:51)
called from Sub 'parrot;Data::Dumper;dumper' pc 63 (/home/doughera/src/parrot/parrot-andy/runtime/parrot/library/Data/Dumper.pir:33)
called from Sub '_dumper' pc 41 (library/dumper.pir:84)
called from Sub 'test' pc 188 (t/library/dumper_1.pir:18)
Finally, here is the full list of failures: (And yes, the goofy summary line
indeed does come out at the wrong spot, exactly as included here.)
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/compilers/pge/p5regexp/p5rx.t 254 65024 800 378 47.25% 1-77 82-98
101-134 137
145-147 150-
154 156-166
168-171 173-
183 185-222
224-231 235-
240 242 245
250-251 255
258-259 262-
263 399-407
409-418 420-
421 423-427
430-431 433-
434 437-438
441-443 450-
451 456-457
481-482 486
494 497 499
513-514 516-
521 525-526
529-530 533-
535 537-539
542 546-547
550-552 555
558-562 565
567 608 618-
620 622 626
636-638 640
644 654-662
672-680 690-
692 694 698
708-716 726-
734 744-746
748 752 762-
770 780-788
798-799
t/compilers/pge/p6rules/backtrack 21 5376 21 21 100.00% 1-21
t/compilers/pge/p6rules/builtins. 68 17408 73 68 93.15% 1-60 63-70
t/compilers/pge/p6rules/capture.t 45 11520 45 45 100.00% 1-45
t/compilers/pge/p6rules/cclass.t 58 14848 62 58 93.55% 1-18 20-55 57-
60
t/compilers/pge/p6rules/closure.t 6 1536 6 6 100.00% 1-6
t/compilers/pge/p6rules/context.t 19 4864 20 19 95.00% 1-15 17-20
t/compilers/pge/p6rules/metachars 192 49152 208 192 92.31% 1-65 68 70-78
81 85 87 89-95
97-101 107-208
t/compilers/pge/p6rules/modifiers 94 24064 98 94 95.92% 1-86 88-91 93-
96
t/compilers/pge/p6rules/subrules. 6 1536 6 6 100.00% 1-6
t/compilers/pge/p6rules/text_brk. 11 2816 12 11 91.67% 2-12
t/compilers/pge/pge-hs.t 1 256 1 1 100.00% 1
t/compilers/pge/pge_examples.t 2 512 2 2 100.00% 1-2
t/compilers/pge/pge_globs.t 22 5632 22 22 100.00% 1-22
t/compilers/pge/pge_util.t 1 256 1 1 100.00% 1
t/compilers/tge/basic.t 2 512 3 2 66.67% 1 3
t/compilers/tge/grammar.t 1 256 1 1 100.00% 1
t/compilers/tge/parser.t 1 256 1 1 100.00% 1
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/library/dumper.t 24 6144 26 24 92.31% 1-15 18-26
t/library/test_more.t 1 256 30 8 26.67% 27-30
t/op/calling.t 1 256 92 1 1.09% 91
t/op/jitn.t 2 512 14 2 14.29% 8 11
t/pmc/complex.t 6 1536 53 6 11.32% 32-33 42-43
46-4Failed 28/233 test scripts, 87.98% okay. 972/4650 subtests failed, 79.10% okay.
7
t/pmc/intlist.t 2 512 10 2 20.00% 3-4
t/pmc/objects.t 2 512 73 2 2.74% 62 73
t/pmc/resizablebooleanarray.t 1 256 21 1 4.76% 16
t/pmc/resizablestringarray.t 1 256 28 1 3.57% 21
t/src/hash.t 1 256 11 1 9.09% 6
11 tests and 387 subtests skipped.
--
Andy Dougherty doug...@lafayette.edu
Patrick R. Michaud
> Something's gone horribly wrong after the recent PGE check-in. I don't
> actually think it's in PGE, just that the new PGE is triggering some other
> bugs elsewhere in parrot (that have been showing up in t/library/dumper.t
> recently). I don't recall such problems in parrot-0.4.2. I didn't test
> parrot-0.4.3.
>
> The first sign of trouble is during the build process:
It seems to be working for me -- could you give us more details
about your build environment? OS, Platform, etc?
I will note that I've noticed a few oddities in dealing with Hashes
and PMCs lately, but nothing that I've been able to boil down to a
reasonable test case.
Pm
Andy Dougherty
> On Fri, Apr 28, 2006 at 11:02:53AM -0400, Andy Dougherty wrote:
> > Something's gone horribly wrong after the recent PGE check-in. I don't
> > actually think it's in PGE, just that the new PGE is triggering some other
> > bugs elsewhere in parrot (that have been showing up in t/library/dumper.t
> > recently). I don't recall such problems in parrot-0.4.2. I didn't test
> > parrot-0.4.3.
> >
> > The first sign of trouble is during the build process:
>
> It seems to be working for me -- could you give us more details
> about your build environment? OS, Platform, etc?
Oh, yes, sorry about that. This is Solaris 8/SPARC with Sun's C compiler.
As I said, I don't think it's PGE itself, but rather that PGE is running
into some more basic problem. On further investigation, I've found that
the t/library_dumper.t problems were also present in parrot-0.4.3, but not
in parrot-0.4.2.
The failures also seem at least superficially similar to those I've
reported in languages/punie/past* (see [perl #38406]).
On a possibly-related, but also possibly-unrelated note, I'm also getting
a failure on test t/pmc/objects_62.pasm:
# Failed test (t/pmc/objects.t at line 1866)
# got: '11
# 11
# 20
# 21
# 11
# 20
# '
# expected: '10
# 11
# 20
# 21
# 10
# 20
# '
This looks similar, but this test was also failing for me in 0.4.2, so it
may be unrelated.
> I will note that I've noticed a few oddities in dealing with Hashes
> and PMCs lately, but nothing that I've been able to boil down to a
> reasonable test case.
I know the feeling, have spent way too much time this week chasing a core
dump in t/src/hash_6.c.
--
Andy Dougherty doug...@lafayette.edu