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 16:39:03 UTC
[jira] [Created] (YARN-155) TestAppManager fails on jdk7
Thomas Graves created YARN-155:
----------------------------------
Summary: TestAppManager fails on jdk7
Key: YARN-155
URL: https://issues.apache.org/jira/browse/YARN-155
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 0.23.3
Reporter: Thomas Graves
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
[jira] [Assigned] (YARN-155) TestAppManager intermittently fails
with jdk7
Posted by "Thomas Graves (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Graves reassigned YARN-155:
----------------------------------
Assignee: Thomas Graves
> 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
> Assignee: 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
[jira] [Commented] (YARN-155) TestAppManager intermittently fails
with jdk7
Posted by "Thomas Graves (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474990#comment-13474990 ]
Thomas Graves commented on YARN-155:
------------------------------------
The issue appears to be that the tests expect the initial app event type to be RMAppEventType.KILL and since with jdk7 the order of tests in random, the last test testRMAppSubmitError is sometimes being called before the others and it doesn't reset the type back to RMAppEventType.KILL. I put in a @After routine to always reset it after each test.
> 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
> Assignee: 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
[jira] [Commented] (YARN-155) TestAppManager intermittently fails
with jdk7
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475006#comment-13475006 ]
Hadoop QA commented on YARN-155:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12548890/YARN-155.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-YARN-Build/87//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/87//console
This message is automatically generated.
> 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
> Assignee: Thomas Graves
> Labels: java7
> Attachments: YARN-155.patch
>
>
> 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
[jira] [Updated] (YARN-155) TestAppManager intermittently fails
with jdk7
Posted by "Thomas Graves (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (YARN-155) TestAppManager intermittently fails
with jdk7
Posted by "Thomas Graves (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Graves updated YARN-155:
-------------------------------
Attachment: YARN-155.patch
> 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
> Assignee: Thomas Graves
> Labels: java7
> Attachments: YARN-155.patch
>
>
> 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
[jira] [Updated] (YARN-155) TestAppManager intermittently fails
with jdk7
Posted by "Thomas Graves (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Graves updated YARN-155:
-------------------------------
Affects Version/s: 2.0.3-alpha
3.0.0
> 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
[jira] [Commented] (YARN-155) TestAppManager intermittently fails
with jdk7
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505666#comment-13505666 ]
Hadoop QA commented on YARN-155:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12548890/YARN-155.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-YARN-Build/181//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/181//console
This message is automatically generated.
> 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
> Assignee: Thomas Graves
> Labels: java7
> Attachments: YARN-155.patch
>
>
> 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