Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of pavel.n.afremov@gmail.com
 designates 64.233.182.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=C4cITTUyKuF6L3MpIDcLZ1cxc6jGhIQ/5ZjTjASQuZnkI7gHZSFjVzwAaZL7fZe7hvEzf5JZhDuqC9vpgnHzA9eVEMliHFhXpwqcQOT/fbSnivDfphuEjN/YQl1KxzwwOgltjtH2KX+fGrRxP9fUNMhlyXFmTgLM3ioaJ6ilQeE=
Message-ID: <783bf8b0610240716r11a132fax94d075ec25b8001e@mail.gmail.com>
Date: Tue, 24 Oct 2006 18:16:23 +0400
From: "Pavel Afremov" <pavel.n.afremov@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: [dlrvm] ClassCircularityError in recursive compilation (Was: Re:
 [drlvm] smoke test : gc PhantomReferenceQueueTest is really unstable)
In-Reply-To: <ehl3ku$mnh$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_9935_21427551.1161699383915"
References: <e0f125db0610110515t1f75e58ew979e49a8a5d853d6@mail.gmail.com>
	 <bc79dd600610240132x68d4b18ds95b6cd756ad84757@mail.gmail.com>
	 <ehkuld$38b$1@sea.gmane.org> <200610241658.51107.gshimansky@gmail.com>
	 <ehl3ku$mnh$1@sea.gmane.org>

------=_Part_9935_21427551.1161699383915
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Salikh,

gc.Finalizer and gc PhantomReferenceQueueTest are synthetic test. And can't
be called "normal" (do code review, if you doubt, please). But this test
isn't source of the circularity error. The error can happen for usual
application too. The CL an SM tests just show that source of fake
circularity error exists. It's it.

I think, this fake error can happen in usual applications. But it can be
masked here or be covered by other issues...

Pavel Afremov


On 10/24/06, Salikh Zakirov <Salikh.Zakirov@intel.com> wrote:
>
> Gregory Shimansky wrote:
> > Yes the test is synthetic. But the whole problem arose from the
> currently
> > excluded smoke tests gc.PhantomReferenceQueueTest and gc.Finalizer. They
> too
> > are synthetic but may be an example of another place where this problem
> > appears.
> >
> > The idea to write user code tests was just to show that finalizers
> > implementation is not the one to be blamed and the problem is
> reproducible on
> > pure user code applications, not to show that this problem is so rare no
> one
> > in right mind would ever write an application to encounter it :)
>
> Gregory,
>
> the problem as I see it is that gc.Finalizer and
> gc.PhantomReferenceQueueTest
> are *normal* test cases in the sense that they exercise finalizable
> objects
> and phantom references in *exactly* the same way as an application would.
>
> And Pavel's synthetic tests (HARMONY-1945) do something allowed by the
> spec, but entirely
> uncommon for an application -- recursive call from a classloader to the
> application.
>
>

------=_Part_9935_21427551.1161699383915--