You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Ol...@Sun.COM on 2007/04/26 16:23:52 UTC
Regression Test Report - tinderbox_trunk16 532695 - Sun DBTG
[Auto-generated mail]
*tinderbox_trunk16* 532695/2007-04-26 12:42:43 CEST
Failed Tests OK Skip Duration Suite
-------------------------------------------------------
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
10 324 314 0 93.04% derbyall
0 7468 7468 0 1341.18% org.apache.derbyTesting.functionTests.suites.All
Details in http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/testSummary-532695.html
Attempted failure analysis in
http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/FailReports/532695_bySig.html
-------------------------------------------------------
Changes in http://dbtg.thresher.com/derby/test/tinderbox_trunk16/UpdateInfo/532695.txt
( All results in http://dbtg.thresher.com/derby/test/ )
Re: Regression Test Report - tinderbox_trunk16 532695 - Sun DBTG
Posted by Kn...@Sun.COM.
Knut.Hatlen@Sun.COM writes:
> Ole.Solberg@Sun.COM writes:
>
>> [Auto-generated mail]
>>
>> *tinderbox_trunk16* 532695/2007-04-26 12:42:43 CEST
>>
>> Failed Tests OK Skip Duration Suite
>> -------------------------------------------------------
>> *Jvm: 1.6*
>> SunOS-5.10_i86pc-i386
>> 10 324 314 0 93.04% derbyall
>
> This could be my fault. I added an assert which made one of the test
> cases in the store tests behave differently in sane and insane
> builds. Thought I had tested all combinations, but obviously not well
> enough... Will see if I can fix it.
Hopefully fixed in revision 532838. Sorry for the noise!
--
Knut Anders
Re: Regression Test Report - tinderbox_trunk16 532695 - Sun DBTG
Posted by Kn...@Sun.COM.
Ole.Solberg@Sun.COM writes:
> [Auto-generated mail]
>
> *tinderbox_trunk16* 532695/2007-04-26 12:42:43 CEST
>
> Failed Tests OK Skip Duration Suite
> -------------------------------------------------------
> *Jvm: 1.6*
> SunOS-5.10_i86pc-i386
> 10 324 314 0 93.04% derbyall
This could be my fault. I added an assert which made one of the test
cases in the store tests behave differently in sane and insane
builds. Thought I had tested all combinations, but obviously not well
enough... Will see if I can fix it.
--
Knut Anders