db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3258) 'Unexpected row count: expected:<0> but was:<3>' in testReleaseCompileLocks
Date Wed, 01 Dec 2010 20:13:11 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-3258:
--------------------------------------

    Attachment: d3258.diff

I am able to reproduce this fairly quickly in my environment if I start five threads running
this test in a loop. Most of the time it's the assert on line 146 that fails, but sometimes
it's the assert on line 140.

With the attached patch, which makes the test wait for the post commit thread to complete
before it queries the lock table, I'm not able to reproduce the failure anymore.

> 'Unexpected row count: expected:<0> but was:<3>' in testReleaseCompileLocks
> ---------------------------------------------------------------------------
>
>                 Key: DERBY-3258
>                 URL: https://issues.apache.org/jira/browse/DERBY-3258
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.4.1.3
>         Environment: OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27
> VJM: Sun Microsystems Inc. 1.6.0-b105
>            Reporter: Ole Solberg
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: d3258.diff
>
>
> Seen in http://dbtg.thresher.com/derby/test/trunk16/jvmAll/testing/Limited/testSummary-601462.html
: JDK16Jvm1.6SunOS-5.11 i86pc-i386.
> There was 1 failure:
> 1) testReleaseCompileLocks(org.apache.derbyTesting.functionTests.tests.lang.ReleaseCompileLocksTest)junit.framework.AssertionFailedError:
Unexpected row count: expected:<0> but was:<3>
> 	at org.apache.derbyTesting.junit.JDBC.assertDrainResults(JDBC.java:596)
> 	at org.apache.derbyTesting.junit.JDBC.assertEmpty(JDBC.java:490)
> 	at org.apache.derbyTesting.functionTests.tests.lang.ReleaseCompileLocksTest.testReleaseCompileLocks(ReleaseCompileLocksTest.java:146)
> 	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:95)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message