[jira] Commented: (DERBY-3218) Around 200 (~ 4%) junit fixtures fail when running 10.3 branch (596744) against 10.3.1.4 derbyTesting.jar using junit-all-codeline-jars

["Daniel John Debrunner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544044 ] 

Daniel John Debrunner commented on DERBY-3218:
----------------------------------------------

The first failure in jdbcapi.._Suite comes after ConcurrencyTest. Looking at its tearDown() method it seems that it executes a DROP TABLE statement but does not call commit and thus rollback() will be called by the super-class' tearDown. Seems like the tearDown() in ConcurrencyTest should be calling commit (and not catching SQLException). I don't see why this would fail using 10.3.1.4's testing jar and not the current version, could be just a coincidence.

> Around 200 (~ 4%) junit fixtures fail when running 10.3 branch (596744) against 10.3.1.4 derbyTesting.jar using junit-all-codeline-jars
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3218
>                 URL: https://issues.apache.org/jira/browse/DERBY-3218
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.1.5
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>         Attachments: TEST-org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite.xml, TEST-org.apache.derbyTesting.functionTests.tests.lang._Suite.xml, TEST-org.apache.derbyTesting.functionTests.tests.tools._Suite.xml, TEST-org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite.xml
>
>
> Investigate reason for failures.
> derbyTesting.jar from 10.3.1.4 can be seen as an existing application that ideally should work when run against a newer version.
> Some failures might be due to valid reasons such as change in SQL States.
> Significant number of the failures seem to be due to the inability of the junit clean database code to drop a schema due to it not being empty.
> AutoLoadTest failing can be ignored, it failed against 10.3.1.4 and has now been fixed (as a test bug) in 10.3.

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