[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540337#comment-14540337 ]
Hudson commented on YARN-3613: ------------------------------ FAILURE: Integrated in Hadoop-trunk-Commit #7808 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7808/]) YARN-3613. TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods. (nijel via kasha) (kasha: rev fe0df596271340788095cb43a1944e19ac4c2cf7) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/TestContainerManagerSecurity.java > TestContainerManagerSecurity should init and start Yarn cluster in setup > instead of individual methods > ------------------------------------------------------------------------------------------------------ > > Key: YARN-3613 > URL: https://issues.apache.org/jira/browse/YARN-3613 > Project: Hadoop YARN > Issue Type: Improvement > Components: test > Affects Versions: 2.7.0 > Reporter: Karthik Kambatla > Assignee: nijel > Priority: Minor > Labels: newbie > Fix For: 2.8.0 > > Attachments: YARN-3613-1.patch, yarn-3613-2.patch > > > In TestContainerManagerSecurity, individual tests init and start Yarn > cluster. This duplication can be avoided by moving that to setup. > Further, one could merge the two @Test methods to avoid bringing up another > mini-cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)