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/30 15:20:00 UTC
[jira] [Created] (OOZIE-3269) Flaky tests in
TestCoordMaterializeTriggerService class
Peter Bacsko created OOZIE-3269:
-----------------------------------
Summary: Flaky tests in TestCoordMaterializeTriggerService class
Key: OOZIE-3269
URL: https://issues.apache.org/jira/browse/OOZIE-3269
Project: Oozie
Issue Type: Sub-task
Components: coordinator, core, tests
Reporter: Peter Bacsko
Assignee: Peter Bacsko
The tests in TestCoordMaterializeTriggerService can fail with various problems.
For example, {{testCoordMaterializeTriggerService3}} typically fails with:
{noformat}
junit.framework.AssertionFailedError: expected:<PREP> but was:<RUNNING>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at org.apache.oozie.service.TestCoordMaterializeTriggerService.testCoordMaterializeTriggerService3(TestCoordMaterializeTriggerService.java:151)
{noformat}
The reason is that {{CoordMaterializeTriggerService}} is running in the background which is what we're trying to test and it interferes with the test execution. Therefore it must be disabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)