You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2013/10/23 22:29:45 UTC

[jira] [Updated] (OOZIE-1596) TestOozieMySqlDBCLI.testCreateMysql fails when tests are executed in a different order

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

Robert Kanter updated OOZIE-1596:
---------------------------------

    Attachment: OOZIE-1596.patch

I verified that it fixes the problem by forcing the tests to run in the "bad" order.

> TestOozieMySqlDBCLI.testCreateMysql fails when tests are executed in a different order
> --------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1596
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1596
>             Project: Oozie
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Minor
>         Attachments: OOZIE-1596.patch
>
>
> {{TestOozieMySqlDBCLI.testCreateMysql}} will fail if the tests are executed in a different order.
> TestOozieMySqlDBCLI.testCreateMysql relies on the default setting of {{FakeConnection.CREATE}} (which is {{true}}), but if {{TestOozieMySqlDBCLI.testUpgradeMysql}} is executed first, it will change {{FakeConnection.CREATE}} to {{false}}, and {{TestOozieMySqlDBCLI.testCreateMysql}} will fail.



--
This message was sent by Atlassian JIRA
(v6.1#6144)