[ https://issues.apache.org/jira/browse/YARN-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589355#comment-13589355 ]
Hadoop QA commented on YARN-434: -------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12571375/YARN-434-trunk.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 tests included appear to have a timeout.{color} {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-common-project/hadoop-common. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/446//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/446//console This message is automatically generated. > fix coverage org.apache.hadoop.fs.ftp > -------------------------------------- > > Key: YARN-434 > URL: https://issues.apache.org/jira/browse/YARN-434 > Project: Hadoop YARN > Issue Type: Test > Affects Versions: 3.0.0, 0.23.7, 2.0.4-beta > Environment: fix coverage org.apache.hadoop.fs.ftp > Reporter: Aleksey Gorshkov > Attachments: YARN-434-trunk.patch > > > fix coverage org.apache.hadoop.fs.ftp > patch YARN-434-trunk.patch for trunk, branch-2, branch-0.23 -- 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