Failure in BlobClob4BlobTest due to wrong results being returned

• Key: DERBY-4135
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Critical
• Assignee: Kristian Waagan
• Reporter: Suran Jayathilaka
• Component/s: Test
• Fix Version/s: 10.5.1.1, 10.6.0.0

Description

This bug was found when doing soft upgrade testing from Derby version 10.4.2.0 to 10.5.1.0 (RC1)

The assertion failure is caused by wrong results being returned.

Steps to reproduce are as follows.

1. Run setEmbeddedCP.bat from version 10.4.2.0's bin folder
2. In a test folder run ij
3. create system/wombat database.
    ij> connect 'jdbc:derby:system/wombat;create=true';
4. exit ij
5. Copy the 10.5.1.0 derby jars (from lib folder) and the derbyTesting.jar from 10.4.2.0 to the test folder and set classpath with them (including junit and ORO)
6. Run testcase
     java -Xmx512M -Xms512M -Dderby.tests.trace=true junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest

The stack trace specific to this failure is as follows.
----------------------------------------------------------------------
3) testUnconsumedParameter(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.AssertionFailedError: Column value mismatch @ column '1', row 1:
    Expected: >38000<
    Found: >38002<
at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1094)
at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1006)
at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:894)
at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:832)
at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:790)
at org.apache.derbyTesting.junit.JDBC.assertSingleValueResultSet(JDBC.java:775)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest.testUnconsumedParameter(BlobClob4BlobTest.java:179)
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:102)
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 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)
----------------------------------------------------------------------------------

This failure can be seen when running this test as part of suites.All as well.

Comments

[Kristian Waagan]

I believe this has already been fixed under DERBY-4122, by patch 1a.

[Kristian Waagan]

Resolving as fixed (revision 759153 in trunk, revision 760820 on the 10.5 branch).
The fix still has to be confirmed and closed, but maybe it would be better to wait for 10.5 RC2 to do that.