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/23 09:09:00 UTC

[jira] [Commented] (OOZIE-3238) Flaky test TestStatusTransitService#testBundleStatusTransitWithLock

    [ https://issues.apache.org/jira/browse/OOZIE-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486942#comment-16486942 ] 

Peter Bacsko commented on OOZIE-3238:
-------------------------------------

Root cause is this part:

{code}
        synchronized (lockThread) {
            lockThread.notifyAll();
        }
        sleep(1000);
        runnable.run();
{code}

{{lockThread.notifyAll()}} lets the locker thread continue which releases the {{LockToken}}. Unfortunately, the hard-wired sleep (again) is not always enough, especially on a slow computer.

> Flaky test TestStatusTransitService#testBundleStatusTransitWithLock
> -------------------------------------------------------------------
>
>                 Key: OOZIE-3238
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3238
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>
> TestStatusTransitService#testBundleStatusTransitWithLock occasionally fails with the following message:
> {noformat}
> junit.framework.AssertionFailedError: expected:<RUNNINGWITHERROR> but was:<RUNNING>
> 	at org.apache.oozie.service.TestStatusTransitService.testBundleStatusTransitWithLock(TestStatusTransitService.java:1593)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)