[ https://issues.apache.org/jira/browse/HDFS-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695902#comment-13695902 ]
Hadoop QA commented on HDFS-4888: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12590089/HDFS-4888.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 2 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-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/4576//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4576//console This message is automatically generated. > Refactor and fix FSNamesystem.getTurnOffTip to sanity > ----------------------------------------------------- > > Key: HDFS-4888 > URL: https://issues.apache.org/jira/browse/HDFS-4888 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 3.0.0, 2.0.4-alpha, 0.23.9 > Reporter: Ravi Prakash > Assignee: Ravi Prakash > Attachments: HDFS-4888.patch, HDFS-4888.patch, HDFS-4888.patch > > > e.g. When resources are low, the command to leave safe mode is not printed. > This method is unnecessarily complex -- 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