On Fri, 28 Apr 2006, Patrick R. Michaud wrote:
> 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 [EMAIL PROTECTED]
