You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2012/10/11 17:43:02 UTC
[jira] [Updated] (YARN-155) TestAppManager intermittently fails
with jdk7
[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Graves updated YARN-155:
-------------------------------
Summary: TestAppManager intermittently fails with jdk7 (was: TestAppManager fails on jdk7)
> TestAppManager intermittently fails with jdk7
> ---------------------------------------------
>
> Key: YARN-155
> URL: https://issues.apache.org/jira/browse/YARN-155
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 0.23.3, 3.0.0, 2.0.3-alpha
> Reporter: Thomas Graves
> Labels: java7
>
> Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.851 sec <<< FAILURE!
> testRMAppSubmit(org.apache.hadoop.yarn.server.resourcemanager.TestAppManager) Time elapsed: 0.017 sec <<< FAILURE!
> junit.framework.AssertionFailedError: app event type is wrong before expected:<KILL> but was:<APP_REJECTED>
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.failNotEquals(Assert.java:283)
> at junit.framework.Assert.assertEquals(Assert.java:64)
> at org.apache.hadoop.yarn.server.resourcemanager.TestAppManager.setupDispatcher(TestAppManager.java:329)
> at org.apache.hadoop.yarn.server.resourcemanager.TestAppManager.testRMAppSubmit(TestAppManager.java:354)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> I can reproduce the failure on jdk6 if I move the testRMAppSubmit to the bottom of the file, so my initial hunch is this is due to test order.
--
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