You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Peter Bacsko (JIRA)" <ji...@apache.org> on 2018/05/16 11:01:00 UTC

[jira] [Commented] (OOZIE-3226) Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError

    [ https://issues.apache.org/jira/browse/OOZIE-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477230#comment-16477230 ] 

Peter Bacsko commented on OOZIE-3226:
-------------------------------------

Yes, it started to fail after OOZIE-3192, although it's not directly caused by that change.

I can see two problems:
1. The method {{setUp()}} is marked with {{@BeforeClass}} but it does not have any effect, because JUnit3 test runner is selected for this class. The annotation is ignored.
2. Therefore {{setUp()}} runs again before {{testOozieDBCLI}} but this time the Derby database is not re-created. I'm not sure why, perhaps something is stored in a static field which prevents Derby from creating the database files again.

Anyway the root cause has been found and I'll upload the fix soon.

> Test case testOozieDBCLI() in oozie-tools fails with junit.framework.AssertionFailedError
> -----------------------------------------------------------------------------------------
>
>                 Key: OOZIE-3226
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3226
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: tools
>         Environment: uname -a
> Linux pts00607-vm3 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:46 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
>            Reporter: Alisha Prabhu
>            Assignee: Peter Bacsko
>            Priority: Major
>
> Maven command used is : mvn -Dtest=TestOozieDBCLI test
> The test case testOozieDBCLI() in oozie-tools fails in the presence of the test case testServicesDestroy()
> {code:java}
> [INFO] Running org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 33.539 s <<< FAILURE! - in org.apache.oozie.tools.TestOozieDBCLI
> [ERROR] testOozieDBCLI(org.apache.oozie.tools.TestOozieDBCLI)  Time elapsed: 4.289 s  <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
>         at org.apache.oozie.tools.TestOozieDBCLI.testOozieDBCLI(TestOozieDBCLI.java:123)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   TestOozieDBCLI.testOozieDBCLI:123 expected:<0> but was:<1>
> [INFO]
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)