Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4D795F58.7070008@sbcglobal.net>
Date: Thu, 10 Mar 2011 15:31:36 -0800
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: lots of regression test errors on Java 7
References: <4D74E7BE.9040804@oracle.com> <4D74F7A3.6070503@oracle.com>
 <wjo8zkp7szkw.fsf@oracle.com>
In-Reply-To: <wjo8zkp7szkw.fsf@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 3/7/2011 7:46 AM, Knut Anders Hatlen wrote:
> The Java 7 installation on the regression test machines was updated from
> 1.7.0-ea-b116 to 1.7.0-ea-b131 on the day these failures started
> happening. I haven't been able to reproduce the failures in my
> environment when running the tests separately. I'll start suites.All
> with the same version and see if the failures can be reproduced then.
>
Thank you Knut for looking at the java 7 issues,

The Derby regression suite has always been  notoriously good at finding 
JVM issues, especially in areas like JIT.  For  JDK development, 
periodic runs of the derby tests on a  branch  where they are stable can 
be a valuable tool. I have also seen the tests run with all sorts of 
interesting jit and other options to stress certain aspects of the JVM 
and pop issues.  It might benefit the OpenJDK  community  to incorporate 
Derby tests into their normal test strategy and can also make life 
easier when you pick up a drop for Derby testing.    The downside is you 
might have to backport test fixes that they encounter to whatever branch 
they run on for things like the ordering issue.


Kathey