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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2013/09/25 18:22:03 UTC
[jira] [Commented] (DERBY-6146) nightly regression test failure:
testMultipleLastKeyWaitsInMaxScan(org.apache.derbyTesting.functionTests.tests.store.IndexSplitDeadlockTest)junit.framework.AssertionFailedError:
Column value mismatch @ column '1',
[ https://issues.apache.org/jira/browse/DERBY-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777699#comment-13777699 ]
Kathey Marsden commented on DERBY-6146:
---------------------------------------
So looking at the test we have
// Give the other thread a little while to start and obtain the
// lock on the last record.
Thread.sleep(1000);
// The last record should be locked now, so this call will have to
// wait initially. This statement used to cause an assert failure in
// debug builds before DERBY-4193.
JDBC.assertSingleValueResultSet(
s.executeQuery("select max(x) from max_scan " +
"--DERBY-PROPERTIES index=IDX"),
"4");
Where the thread that we are waiting for inserts the 4 that we expect to see. So maybe the Thread.sleep(1000) is just not long enough sometimes. Perhaps the test should synchronize the two threads in a different way.
I will try first eliminating the sleep to see if it makes the failure more likely to happen.
> nightly regression test failure: testMultipleLastKeyWaitsInMaxScan(org.apache.derbyTesting.functionTests.tests.store.IndexSplitDeadlockTest)junit.framework.AssertionFailedError: Column value mismatch @ column '1',
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6146
> URL: https://issues.apache.org/jira/browse/DERBY-6146
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.3.1, 10.9.2.2
> Environment: windows, ibm16
> Reporter: Mike Matrigali
>
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/windows/testlog/ibm16/1461387-suites.All_diff.txt
> 1) testMultipleLastKeyWaitsInMaxScan(org.apache.derbyTesting.functionTests.tests.store.IndexSplitDeadlockTest)junit.framework.AssertionFailedError: Column value mismatch @ column '1', row 1:
> Expected: >4<
> Found: >3<
> at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1213)
> at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1125)
> at org.apache.derbyTesting.junit.JDBC.assertFullResultSetMinion(JDBC.java:1012)
> at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:935)
> at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:892)
> at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:850)
> at org.apache.derbyTesting.junit.JDBC.assertSingleValueResultSet(JDBC.java:835)
> at org.apache.derbyTesting.functionTests.tests.store.IndexSplitDeadlockTest.testMultipleLastKeyWaitsInMaxScan(IndexSplitDeadlockTest.java:657)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:110)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> FAILURES!!!
> Tests run: 15197, Failures: 1, Errors: 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira