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 22:49:42 GMT

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

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

In fact the test that seems to lead to the DROP SCHEMA failures is tools/ToolScripts and specifically
the ij7.sql script.

This passes in the latest 10.3.

The 10.3.1.4 testing.jar fails against the latest 10.3 code.

The latest 10.3.1.4 testing jar fails against the 10.3.1.4 jar files.

Also seems that the test has not been modified in 10.3 branch







> 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