Major Description
Unit tests based on WorkflowTestCase are flaky. For instance TestWorkflow.testWorkflowWithStartAndEndCompletesSuccessfully failed here: https://builds.apache.org/job/PreCommit-OOZIE-Build/1120/
15:06:19 [ERROR] testWorkflowWithStartAndEndCompletesSuccessfully(org.apache.oozie.test.TestWorkflowRetries) Time elapsed: 2.622 s <<< FAILURE! 15:06:19 junit.framework.AssertionFailedError: expected:<RUNNING> but was:<SUCCEEDED> 15:06:19 at junit.framework.Assert.fail(Assert.java:57) 15:06:19 at junit.framework.Assert.failNotEquals(Assert.java:329) 15:06:19 at junit.framework.Assert.assertEquals(Assert.java:78) 15:06:19 at junit.framework.Assert.assertEquals(Assert.java:86) 15:06:19 at junit.framework.TestCase.assertEquals(TestCase.java:253) 15:06:19 at org.apache.oozie.test.WorkflowTestCase$WorkflowJobBuilder.start(WorkflowTestCase.java:241) 15:06:19 at org.apache.oozie.test.WorkflowTestCase$WorkflowJobBuilder.access$200(WorkflowTestCase.java:161) 15:06:19 at org.apache.oozie.test.WorkflowTestCase.submitAndAssert(WorkflowTestCase.java:51) 15:06:19 at org.apache.oozie.test.TestWorkflow.testWorkflowWithStartAndEndCompletesSuccessfully(TestWorkflow.java:39)
It's not a good idea that WorkflowTestCase.start expects a RUNNING status, it's possible that the workflow is already finished at this point.