Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of xu.regis@gmail.com designates
 64.233.166.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=kUijDgfmCFLXHZkzw9zGGeQ5Gf9PipHgYFw0200SKaAHUPIzktd5Q9AqfEtyN3op6CCefIND3mXvprwgoL+2+IwAnJGO3MvHT4FpERd0xuAFoYQiLvLJULztaagMbetDDezkDWQcsvqLlPQNc9RxgAKzYwi42Q0HG0/mG2oOt1o=
Message-ID: <480D9660.30601@gmail.com>
Date: Tue, 22 Apr 2008 15:40:16 +0800
From: Regis <xu.regis@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: [test][classlib] Does anyone meet all the failures with those
 SQL packages?
References: <9623c9a50804212040s20aea115jc7cbafb20279a5cc@mail.gmail.com>
	 <f944d83d0804212128h8c779c6ya1fcd9d7ba66cc9e@mail.gmail.com>
	 <480D6E39.8050009@gmail.com> <480D829E.4060600@gmail.com>
 <8432f67d0804220026n79a0990aq1027c03c6c16b7b5@mail.gmail.com>
In-Reply-To: <8432f67d0804220026n79a0990aq1027c03c6c16b7b5@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit


Chen Yang wrote:
> I have tried locally with updated classlib and rebuilt with ant clean (Win32
> and Win64). I can still meet lots test failures other than the one that you
> have met, mostly is:
> 
> Create DB Failure!
> 
> java.sql.SQLException: Create DB Failure!
Seems Derby create database failed. Could you give more details of 
exception stack trace?
It would be helpful to see what cause the problem.

Best Regards,
Regis.

> at
> org.apache.harmony.sql.tests.internal.rowset.CachedRowSetTestCase.setUp(CachedRowSetTestCase.java:64)
> 
> --
>  Chen
> 
> On 4/22/08, Regis <xu.regis@gmail.com> wrote:
>>
>> Regis wrote:
>>
>>>
>>> Alexey Varlamov wrote:
>>>
>>>> Integrity testing [1] shows 1 failure in SQL (+7 failures in other
>>>> modules) :
>>>>
>>>> Test:  testUpdateAsciiStream
>>>> Class:
>>>>  org.apache.harmony.sql.tests.internal.rowset.CachedRowSetStreamTest
>>>>  junit.framework.AssertionFailedError: expected:<和谐> but was:<??>
>>>>  at
>>>> org.apache.harmony.sql.tests.internal.rowset.CachedRowSetStreamTest.testUpdateAsciiStream(CachedRowSetStreamTest.java:787)
>>>>
>>>>  at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
>>>>
>>> I found it was failed when the default locale didn't support Chinese
>> characters, even on RI.
>> I think the test case could be rewrite to fit different environments. I
>> have filed a JIRA [1]
>> to trace this issue.
>>
>> [1] https://issues.apache.org/jira/browse/HARMONY-5773
>>
>> Best Regards,
>> Regis.
>>
>>
>>>> I'm looking on this, it seems some locale data cause the failure...
>>> BTW, classlib tests are "RED" since mid-February, does anyone care to
>>>> fix or exclude problematic cases? Here is the current list:
>>>>
>>>> error  testRead
>>>> org.apache.harmony.archive.tests.java.util.jar.ManifestTest
>>>> error  testGetAttribute
>>>> org.apache.harmony.lang.management.MemoryPoolMXBeanImplTest
>>>> error  testGetCollectionUsage
>>>> org.apache.harmony.lang.management.tests.java.lang.management.MemoryPoolMXBeanTest
>>>>
>>>> failure  testStart
>>>> org.apache.harmony.luni.tests.java.lang.ProcessBuilderTest
>>>> failure  test_ConstructorI
>>>> org.apache.harmony.luni.tests.java.net.MulticastSocketTest
>>>> failure  test_ConstructorLjava_util_TimeZone
>>>> org.apache.harmony.luni.tests.java.util.GregorianCalendarTest
>>>> failure  test_ConstructorLjava_util_TimeZoneLjava_util_Locale
>>>> org.apache.harmony.luni.tests.java.util.GregorianCalendarTest
>>>> failure  testUpdateAsciiStream
>>>> org.apache.harmony.sql.tests.internal.rowset.CachedRowSetStreamTest
>>>>
>>>> [1] http://people.apache.org/~varlax/harmony-integrity/
>>>>
>>>> --
>>>> Alexey
>>>>
>>>> 2008/4/22, Xiao-Feng Li <xiaofeng.li@gmail.com>:
>>>>
>>>>> They failed in my local testings with SVN. I don't know if that's a
>>>>> known issue and if that blocks any new commits.
>>>>>
>>>>> Thanks,
>>>>> xiaofeng
>>>>>
>>>>> --
>>>>> http://xiao-feng.blogspot.com
>>>>>
>>>>>
> 
>