db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [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
Date Tue, 20 Nov 2007 23:11:43 GMT

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

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

Found the issue for the DROP SCHEMA failing. DERBY-1790 was correctly fixed in 10.3 (after
10.3.1.4), the 10.3.1.4 tests include a work-around which is no longer valid and the new correct
code in 10.3 latest fails (correctly) against 10.3.1.4)

This is due the DatabaseMetaData.getTables() not support the table type SYNONYM correctly
in 10.3.1.4.

I'll hack up a 10.3.1.4 with just the test code modified and see what failures are left.

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


Mime
View raw message