[
https://issues.apache.org/jira/browse/OOZIE-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488635#comment-15488635
]
Robert Kanter commented on OOZIE-2659:
--------------------------------------
Shouldn't the first change be
{code:java}
return cJob1.getStatus() == Job.Status.PAUSED && cJob2.getStatus() ==
Job.Status.PAUSED;
{code}
not
{code:java}
return cJob1.getStatus() == Job.Status.RUNNING && cJob2.getStatus() ==
Job.Status.RUNNING;
{code}
?
> TestPauseTransitService is flaky
> --------------------------------
>
> Key: OOZIE-2659
> URL: https://issues.apache.org/jira/browse/OOZIE-2659
> Project: Oozie
> Issue Type: Bug
> Reporter: Peter Cseh
> Assignee: Peter Cseh
> Attachments: OOZIE-2659.001.patch
>
>
> In TestPauseTransitService we have some {{waitFor}} calls to let the
> {{PauseTransitRunnable}} do it's job.
> In some places we are waiting for only one job and checking the status of
> two. Sometimes one of the jobs is still paused which causes the test to fail
> If we wait for both, hopefully the test will be more robust.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
