Failure in BlobClob4BlobTest due to wrong results being returned
----------------------------------------------------------------
Key: DERBY-4135
URL: https://issues.apache.org/jira/browse/DERBY-4135
Project: Derby
Issue Type: Bug
Components: Regression Test Failure
Affects Versions: 10.5.1.0
Environment: Windows Vista 64, Sun JDK 1.6.0_10, Junit 3.8.2
Reporter: Suran Jayathilaka
Priority: Critical
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
