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-4301) testGetBinaryStream failed with AssertionFailedError: (expected:<0> but was:<2>) with 10.3 server and 10.5 client testing
Date Thu, 30 Sep 2010 09:58:34 GMT

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

Knut Anders Hatlen updated DERBY-4301:
--------------------------------------

    Issue & fix info: [Repro attached]  (was: [Newcomer])

Adding the repro attached flag. Removing the newcomer flag since the complexity of this issue
is unknown.

> testGetBinaryStream failed with AssertionFailedError: (expected:<0> but was:<2>)
with 10.3 server and 10.5 client testing
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4301
>                 URL: https://issues.apache.org/jira/browse/DERBY-4301
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.1.1
>         Environment: Windows Vista
>            Reporter: Lily Wei
>
> testGetBinaryStream failed with 10.3 server 10.5 client testing.
> It looks like locks being held with testenBinaryStream which does not expect to happen.
> This is the stack trace:
> 1) testGetBinaryStream(org.apache.derbyTesting.functionTests.tests.jdbcapi.Large
> DataLocksTest)junit.framework.AssertionFailedError: expected:<0> but was:<2>
>         at org.apache.derbyTesting.functionTests.tests.jdbcapi.LargeDataLocksTes
> t.testGetBinaryStream(LargeDataLocksTest.java:114)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
>         at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:
> 89)
>         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
> )
>         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
> )
>         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)
> FAILURES!!!
> Tests run: 8,  Failures: 1,  Errors: 0
> How to reproduce this bug:
> 1. Use derbyclient.jar with 10.5 the rest jar files from 10.5
> 2. run 'java junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.jdbcapi.LargeDataLocksTest'

-- 
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