Peter Bacsko created OOZIE-3295:
-----------------------------------
Summary: Flaky test
TestSLACalculatorMemory#testAddMultipleRestartRemoveMultipleInstrumentedCorrectly
Key: OOZIE-3295
URL: https://issues.apache.org/jira/browse/OOZIE-3295
Project: Oozie
Issue Type: Sub-task
Components: core, tests
Reporter: Peter Bacsko
Assignee: Peter Bacsko
The test
TestSLACalculatorMemory.testAddMultipleRestartRemoveMultipleInstrumentedCorrectly
can fail with the following error:
{noformat}
junit.framework.AssertionFailedError: SLA map size after update all should be
2. An instance of SLACalcStatus was removed expected:<2> but was:<1>
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:159)
at junit.framework.TestCase.assertEquals(TestCase.java:316)
at
org.apache.oozie.sla.TestSLACalculatorMemory.testAddMultipleRestartRemoveMultipleInstrumentedCorrectly(TestSLACalculatorMemory.java:1084)
{noformat}
The problem is the following setting:
{noformat}
slaRegBean1.setExpectedDuration(123);
{noformat}
The expected duration should not be set for such a small value (123 msecs). On
a slow machine, SLA calculator might detect that this particular SLA has been
missed. It must be increased to a higher value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
