You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/01/06 17:45:56 UTC

[jira] [Updated] (DERBY-6446) Test ordering problem in GrantRevokeDDLTest

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

Rick Hillegas updated DERBY-6446:
---------------------------------

    Attachment: derby-6446-01-aa-filterUnwantedSchema.diff

Attaching derby-6446-01-aa-filterUnwantedSchema.diff. This patch filters out the new schema name from queries against SYS.SYSSCHEMAS.

Touches the following file:

M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/GrantRevokeDDLTest.java


> Test ordering problem in GrantRevokeDDLTest
> -------------------------------------------
>
>                 Key: DERBY-6446
>                 URL: https://issues.apache.org/jira/browse/DERBY-6446
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-6446-01-aa-filterUnwantedSchema.diff
>
>
> Work on DERBY-6429 added a new schema to GrantRevokeDDLTest. If the new test runs before testGrantRevokeDDL(), then that test case will raise an error because of the presence of the extra schema. This turned up in the nightly tests: http://download.java.net/javadesktop/derby/request_5586046/javadb-task-3782065.html



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)