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 2011/04/14 17:55:40 UTC
Regression Test Report - Daily 1091835 - Sun DBTG
[Auto-generated mail]
*Daily* 1091835/2011-04-13 18:00:22 MEST
Failed Tests OK Skip Duration Suite
-------------------------------------------------------
*Jvm: 1.6*
lin
0 13530 13530 0 1320.62% suitesAll
0 15 15 0 .% jdbcapiAutoLoad
0 14 14 0 .% JDBCDriversAll
0 15 15 0 .% JDBCDriversClient
0 14 14 0 .% JDBCDriversEmbedded
0 195 195 0 50.02% derbyall
0 2 2 0 1303.40% compatibility
0 2 2 0 .% demoSuite
sles
NA NA NA NA suitesAll
NA NA NA NA jdbcapiAutoLoad
NA NA NA NA JDBCDriversAll
NA NA NA NA JDBCDriversClient
NA NA NA NA JDBCDriversEmbedded
NA NA NA NA derbyall
NA NA NA NA compatibility
NA NA NA NA demoSuite
sol
0 13520 13520 0 944.83% suitesAll
0 15 15 0 .% jdbcapiAutoLoad
0 14 14 0 .% JDBCDriversAll
0 15 15 0 .% JDBCDriversClient
0 14 14 0 .% JDBCDriversEmbedded
0 195 195 0 38.29% derbyall
0 2 2 0 506.82% compatibility
0 2 2 0 .% demoSuite
sol32
NA NA NA NA suitesAll
NA NA NA NA jdbcapiAutoLoad
NA NA NA NA JDBCDriversAll
NA NA NA NA JDBCDriversClient
NA NA NA NA JDBCDriversEmbedded
NA NA NA NA derbyall
NA NA NA NA compatibility
NA NA NA NA demoSuite
solN+1
0 13520 13520 0 182.42% suitesAll
0 15 15 0 .% jdbcapiAutoLoad
0 14 14 0 .% JDBCDriversAll
0 15 15 0 .% JDBCDriversClient
0 14 14 0 .% JDBCDriversEmbedded
0 195 195 0 57.83% derbyall
0 2 2 0 460.33% compatibility
0 2 2 0 .% demoSuite
sparc
0 13520 13520 0 505.93% suitesAll
0 15 15 0 .% jdbcapiAutoLoad
0 14 14 0 .% JDBCDriversAll
0 15 15 0 .% JDBCDriversClient
0 14 14 0 .% JDBCDriversEmbedded
0 195 195 0 29.57% derbyall
0 2 2 0 469.15% compatibility
0 2 2 0 .% demoSuite
vista
NA NA NA NA suitesAll
NA NA NA NA jdbcapiAutoLoad
NA NA NA NA JDBCDriversAll
NA NA NA NA JDBCDriversClient
NA NA NA NA JDBCDriversEmbedded
NA NA NA NA derbyall
NA NA NA NA compatibility
NA NA NA NA demoSuite
vista-64
NA NA NA NA suitesAll
NA NA NA NA jdbcapiAutoLoad
NA NA NA NA JDBCDriversAll
NA NA NA NA JDBCDriversClient
NA NA NA NA JDBCDriversEmbedded
NA NA NA NA derbyall
NA NA NA NA compatibility
NA NA NA NA demoSuite
w2003
0 13524 13524 0 298.65% suitesAll
0 15 15 0 .% jdbcapiAutoLoad
0 14 14 0 .% JDBCDriversAll
0 15 15 0 .% JDBCDriversClient
0 14 14 0 .% JDBCDriversEmbedded
0 195 195 0 60.51% derbyall
NA NA NA NA compatibility
0 2 2 0 .% demoSuite
Details in http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-1091835.html
Attempted failure analysis in
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/FailReports/1091835_bySig.html
*Jvm: 1.5*
lin
0 196 196 0 44.82% derbyall
0 11621 11621 0 2235.17% suitesAll
sles
NA NA NA NA derbyall
NA NA NA NA suitesAll
sol
0 196 196 0 41.71% derbyall
0 11611 11611 0 1827.71% suitesAll
sol32
NA NA NA NA derbyall
NA NA NA NA suitesAll
solN+1
0 196 196 0 52.06% derbyall
0 11611 11611 0 1835.28% suitesAll
sparc
0 196 196 0 28.86% derbyall
0 11611 11611 0 1193.24% suitesAll
vista
NA NA NA NA derbyall
NA NA NA NA suitesAll
vista-64
NA NA NA NA derbyall
NA NA NA NA suitesAll
w2003
0 196 196 0 51.15% derbyall
NA NA NA NA suitesAll
Details in http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-1091835.html
Attempted failure analysis in
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/FailReports/1091835_bySig.html
*Jvm: 1.4*
lin
0 194 194 2 44.96% derbyall
0 11517 11517 0 2251.14% suitesAll
sles
NA NA NA NA derbyall
NA NA NA NA suitesAll
sol
0 194 194 2 37.43% derbyall
0 11507 11507 0 1810.99% suitesAll
sol32
NA NA NA NA derbyall
NA NA NA NA suitesAll
solN+1
0 194 194 2 52.22% derbyall
0 11507 11507 0 1963.84% suitesAll
sparc
0 194 194 2 27.62% derbyall
0 11507 11507 0 1328.39% suitesAll
vista
NA NA NA NA derbyall
NA NA NA NA suitesAll
vista-64
NA NA NA NA derbyall
NA NA NA NA suitesAll
w2003
0 194 194 2 50.26% derbyall
NA NA NA NA suitesAll
Details in http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-1091835.html
Attempted failure analysis in
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.4/FailReports/1091835_bySig.html
.......................................................
*Jvm: 1.7*
lin
0 13620 13620 0 .% suitesAll
0 15 15 0 .% jdbcapiAutoLoad
0 14 14 0 .% JDBCDriversAll
0 15 15 0 .% JDBCDriversClient
0 14 14 0 .% JDBCDriversEmbedded
0 195 195 0 .% derbyall
NA NA NA NA compatibility
0 2 2 0 .% demoSuite
sol
0 13620 13620 0 .% suitesAll
0 15 15 0 .% jdbcapiAutoLoad
0 14 14 0 .% JDBCDriversAll
0 15 15 0 .% JDBCDriversClient
0 14 14 0 .% JDBCDriversEmbedded
0 195 195 0 .% derbyall
0 2 2 0 .% compatibility
0 2 2 0 .% demoSuite
sol32
NA NA NA NA suitesAll
NA NA NA NA jdbcapiAutoLoad
NA NA NA NA JDBCDriversAll
NA NA NA NA JDBCDriversClient
NA NA NA NA JDBCDriversEmbedded
NA NA NA NA derbyall
NA NA NA NA compatibility
NA NA NA NA demoSuite
vista-64
NA NA NA NA suitesAll
NA NA NA NA jdbcapiAutoLoad
NA NA NA NA JDBCDriversAll
NA NA NA NA JDBCDriversClient
NA NA NA NA JDBCDriversEmbedded
NA NA NA NA derbyall
NA NA NA NA compatibility
NA NA NA NA demoSuite
Details in http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/Limited/testSummary-1091835.html
Attempted failure analysis in
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/FailReports/1091835_bySig.html
*Jvm: phoneME*
ubuntu
NA NA NA NA suitesAll
Details in http://dbtg.foundry.sun.com/derby/test/Daily/javaME/testing/Limited/testSummary-1091835.html
Attempted failure analysis in
http://dbtg.foundry.sun.com/derby/test/Daily/javaME/FailReports/1091835_bySig.html
-------------------------------------------------------
Changes in http://dbtg.foundry.sun.com/derby/test/Daily/UpdateInfo/1091835.txt
( All results in http://dbtg.foundry.sun.com/derby/test/ )
Re: junit failures
Posted by Kristian Waagan <kr...@apache.org>.
On 19.04.11 23:51, Dave Brosius wrote:
> On 04/19/2011 02:39 PM, Kathey Marsden wrote:
>> On 4/19/2011 8:37 AM, Lily Wei wrote:
>>> Hi David:
>>> I tried with an empty directory for the same test with your fix.
>>> It also failed for me with the patch.
>>>
>> So it sounds specifically related to the patch. I wonder if at
>> whatever point these objects are supposed to be dropped, there are
>> open result sets so it doesn't actually get dropped. Is there
>> anything in the derby.log about maybe not being able to drop the
>> Phase table because of open result sets?
>>
>>
>>
>>
> Only thing of interest is this, nothing related to the Phase table:
>
> Sun Apr 17 04:57:15 EST 2011 : Execution failed because of Permanent
> Agent Error: SVRCOD = 40; RDBNAM = srvdscreateshutdowndb1;create=true;
> diagnostic msg = ASSERT FAILED pbsd is not expected to be null
> org.apache.derby.impl.drda.DRDAProtocolException: Execution failed
> because of Permanent Agent Error: SVRCOD = 40; RDBNAM =
> srvdscreateshutdowndb1;create=true; diagnostic msg = ASSERT FAILED
> pbsd is not expected to be null
> at
> org.apache.derby.impl.drda.DRDAProtocolException.newAgentError(DRDAProtocolException.java:339)
> at
> org.apache.derby.impl.drda.DRDAConnThread.sendUnexpectedException(DRDAConnThread.java:8378)
> at
> org.apache.derby.impl.drda.DRDAConnThread.handleException(DRDAConnThread.java:8329)
> at
> org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:319)
> Sun Apr 17 04:57:15 EST 2011 : ASSERT FAILED pbsd is not expected to
> be null
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED
> pbsd is not expected to be null
> at
> org.apache.derby.shared.common.sanity.SanityManager.ASSERT(SanityManager.java:120)
> at
> org.apache.derby.impl.drda.DRDAConnThread.writePBSD(DRDAConnThread.java:2726)
> at
> org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:1044)
> at
> org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:294)
Looking at the stack trace, the assert is related to the piggy-backing
of session state data. This was added as DERBY-3192, and I also made
minor some changes as part of DERBY-3596.
I haven't looked at your patch, so I have no idea what causes the assert
to trigger. Things start looking at may be whether protocol flows have
been changed, or if a deferred reset is taking place.
Out of curiosity, do all the tests pass when you run with an insane
build? [*]
Regards,
--
Kristian
* Even if they pass, a performance regression for the client driver may
have been introduced (typically one extra round-trip to get the session
data).
Re: junit failures
Posted by Dave Brosius <db...@mebigfatguy.com>.
On 04/19/2011 02:39 PM, Kathey Marsden wrote:
> On 4/19/2011 8:37 AM, Lily Wei wrote:
>> Hi David:
>> I tried with an empty directory for the same test with your fix.
>> It also failed for me with the patch.
>>
> So it sounds specifically related to the patch. I wonder if at
> whatever point these objects are supposed to be dropped, there are
> open result sets so it doesn't actually get dropped. Is there anything
> in the derby.log about maybe not being able to drop the Phase table
> because of open result sets?
>
>
>
>
Only thing of interest is this, nothing related to the Phase table:
Sun Apr 17 04:57:15 EST 2011 : Execution failed because of Permanent
Agent Error: SVRCOD = 40; RDBNAM = srvdscreateshutdowndb1;create=true;
diagnostic msg = ASSERT FAILED pbsd is not expected to be null
org.apache.derby.impl.drda.DRDAProtocolException: Execution failed
because of Permanent Agent Error: SVRCOD = 40; RDBNAM =
srvdscreateshutdowndb1;create=true; diagnostic msg = ASSERT FAILED pbsd
is not expected to be null
at
org.apache.derby.impl.drda.DRDAProtocolException.newAgentError(DRDAProtocolException.java:339)
at
org.apache.derby.impl.drda.DRDAConnThread.sendUnexpectedException(DRDAConnThread.java:8378)
at
org.apache.derby.impl.drda.DRDAConnThread.handleException(DRDAConnThread.java:8329)
at
org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:319)
Sun Apr 17 04:57:15 EST 2011 : ASSERT FAILED pbsd is not expected to be null
org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED pbsd
is not expected to be null
at
org.apache.derby.shared.common.sanity.SanityManager.ASSERT(SanityManager.java:120)
at
org.apache.derby.impl.drda.DRDAConnThread.writePBSD(DRDAConnThread.java:2726)
at
org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:1044)
at
org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:294)
Re: junit failures
Posted by Kathey Marsden <km...@sbcglobal.net>.
On 4/19/2011 8:37 AM, Lily Wei wrote:
> Hi David:
> I tried with an empty directory for the same test with your fix.
> It also failed for me with the patch.
>
So it sounds specifically related to the patch. I wonder if at whatever
point these objects are supposed to be dropped, there are open result
sets so it doesn't actually get dropped. Is there anything in the
derby.log about maybe not being able to drop the Phase table because of
open result sets?
Re: junit failures
Posted by Lily Wei <li...@gmail.com>.
Hi David:
I tried with an empty directory for the same test with your fix. It also
failed for me with the patch.
Thanks,
Lily
On Mon, Apr 18, 2011 at 5:03 AM, Knut Anders Hatlen
<kn...@oracle.com>wrote:
> Dave Brosius <db...@apache.org> writes:
>
> > I've managed to knock down the number of failures for running:
> >
> > java -classpath
> >
> tools/java/junit.jar:tools/java/jakarta-oro-2.0.8.jar:jars/sane/derbyTesting.jar:jars/sane/derby.jar:jars/sane/derbyTools.jar:jars/sane/derbyTools.jar:jars/sane/derbyrun.jar:jars/sane/derbynet.jar:jars/sane/derbyclient.jar
> > -Xmx800m -XX:MaxPermSize=512m junit.textui.TestRunner
> > org.apache.derbyTesting.functionTests.suites.All
> >
> > to two, below.
> >
> > Anyone know what i'm doing wrong?
>
> Perhaps you have old databases lying around from earlier test runs? That
> could confuse some of the tests. Removing the system directory before
> rerunning the tests should help if that's the problem.
>
> --
> Knut Anders
>
Re: junit failures
Posted by Knut Anders Hatlen <kn...@oracle.com>.
Dave Brosius <db...@apache.org> writes:
> I've managed to knock down the number of failures for running:
>
> java -classpath
> tools/java/junit.jar:tools/java/jakarta-oro-2.0.8.jar:jars/sane/derbyTesting.jar:jars/sane/derby.jar:jars/sane/derbyTools.jar:jars/sane/derbyTools.jar:jars/sane/derbyrun.jar:jars/sane/derbynet.jar:jars/sane/derbyclient.jar
> -Xmx800m -XX:MaxPermSize=512m junit.textui.TestRunner
> org.apache.derbyTesting.functionTests.suites.All
>
> to two, below.
>
> Anyone know what i'm doing wrong?
Perhaps you have old databases lying around from earlier test runs? That
could confuse some of the tests. Removing the system directory before
rerunning the tests should help if that's the problem.
--
Knut Anders
junit failures
Posted by Dave Brosius <db...@apache.org>.
I've managed to knock down the number of failures for running:
java -classpath
tools/java/junit.jar:tools/java/jakarta-oro-2.0.8.jar:jars/sane/derbyTesting.jar:jars/sane/derby.jar:jars/sane/derbyTools.jar:jars/sane/derbyTools.jar:jars/sane/derbyrun.jar:jars/sane/derbynet.jar:jars/sane/derbyclient.jar
-Xmx800m -XX:MaxPermSize=512m junit.textui.TestRunner
org.apache.derbyTesting.functionTests.suites.All
to two, below.
Anyone know what i'm doing wrong?
1)
testTriggerBasic(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)ERROR
X0Y32: Table/View 'TRIGGER_T1' already exists in Schema 'APP'.
at
org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.duplicateDescriptorException(Unknown
Source)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(Unknown
Source)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(Unknown
Source)
at
org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(Unknown
Source)
at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown
Source)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testTriggerBasic(BasicSetup.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
2)
testDML(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)ERROR
X0Y32: Table/View 'PHASE' already exists in Schema 'APP'.
at
org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.duplicateDescriptorException(Unknown
Source)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(Unknown
Source)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(Unknown
Source)
at
org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(Unknown
Source)
at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown
Source)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.testDML(BasicSetup.java:143)