[
https://issues.apache.org/jira/browse/DERBY-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner updated DERBY-3218:
-----------------------------------------
Attachment:
TEST-org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite.xml
New set of test reports with the SYNONYM issue fixed in the testing jar from
10.3.1.4.
Shows 20 errors and 26 failures.
> 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.derbynet._Suite.xml,
> TEST-org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite.xml,
> TEST-org.apache.derbyTesting.functionTests.tests.lang._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.
