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 10:26:00 UTC

[jira] [Comment Edited] (OOZIE-2967) TestStatusTransitService.testBundleStatusCoordSubmitFails fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT

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

Peter Bacsko edited comment on OOZIE-2967 at 5/23/18 10:25 AM:
---------------------------------------------------------------

This test has an interesting problem: even though certain services are excluded in {{setUp()}}, the {{Service}} object is re-created and re-initialized in the test. It means that {{StatusTransitService}} will be started which sometimes interferes with the test.

There's also a completely unnecessary {{sleep(1000);}}.


was (Author: pbacsko):
This test has an interesting problem: even though certain services are excluded in {{setUp()}}, the {{Service}} object is re-created and re-initialized in the test. It means that {{StatusTransitService}} will be started which sometimes interferes with the test.

> TestStatusTransitService.testBundleStatusCoordSubmitFails fails intermittently in Apache Oozie Core 5.0.0-SNAPSHOT
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-2967
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2967
>             Project: Oozie
>          Issue Type: Sub-task
>          Components: tests
>    Affects Versions: 5.0.0
>         Environment: $ uname -a
> Linux pts00450-vm24 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>            Reporter: Parita Johari
>            Assignee: Peter Bacsko
>            Priority: Major
>             Fix For: 5.1.0
>
>         Attachments: OOZIE-2967-001.patch
>
>
> {code:java}
> Stacktrace
> junit.framework.AssertionFailedError: expected:<FAILED> 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.TestStatusTransitService.testBundleStatusCoordSubmitFails(TestStatusTransitService.java:1647)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at junit.framework.TestCase.runTest(TestCase.java:176)
> 	at junit.framework.TestCase.runBare(TestCase.java:141)
> 	at junit.framework.TestResult$1.protect(TestResult.java:122)
> 	at junit.framework.TestResult.runProtected(TestResult.java:142)
> 	at junit.framework.TestResult.run(TestResult.java:125)
> 	at junit.framework.TestCase.run(TestCase.java:129)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:255)
> 	at junit.framework.TestSuite.run(TestSuite.java:250)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> 	at org.junit.runners.Suite.runChild(Suite.java:127)
> 	at org.junit.runners.Suite.runChild(Suite.java:26)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> {code}



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