[
https://issues.apache.org/jira/browse/OOZIE-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695967#comment-13695967
]
Ryota Egashira commented on OOZIE-1405:
---------------------------------------
Other flaky test is TestSLAEventGeneration.testCoordinatorActionCommands
{code}
new CoordKillXCommand(jobId).call();
ehs.new EventWorker().run();
ehs.getEventQueue().poll(); //ignore duration event
slaEvent = (SLACalcStatus) ehs.getEventQueue().poll();
{code}
slaEvent is null, which cause exception. reason is, actions have been already
in terminal state, and no actions killed in CoordKillXCommand. hence no new
jobevent message pushed to queue.
> Fix flakey SLA tests
> --------------------
>
> Key: OOZIE-1405
> URL: https://issues.apache.org/jira/browse/OOZIE-1405
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: trunk
>
> Attachments: 1405-part.patch
>
>
> The SLA tests keep failing randomly because they rely on Thread.sleep. Would
> be better to execute all test case scenarios and then assert everything in
> order from eventQueue to avoid flakey failures.
> Similar for time-sensitive TestEventGeneration tests e.g. -
> org.apache.oozie.event.TestEventGeneration.testCoordinatorActionEvent
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
