[ https://issues.apache.org/jira/browse/HADOOP-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190498#comment-14190498 ]
Hadoop QA commented on HADOOP-11244: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12678241/HADOOP-11244.patch against trunk revision 73e626a. {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}. There were no new javadoc 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 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-common-project/hadoop-common: org.apache.hadoop.fs.contract.localfs.TestLocalFSContractAppend {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/4990//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/4990//console This message is automatically generated. > The HCFS contract test testRenameFileBeingAppended doesn't do a rename > ---------------------------------------------------------------------- > > Key: HADOOP-11244 > URL: https://issues.apache.org/jira/browse/HADOOP-11244 > Project: Hadoop Common > Issue Type: Bug > Components: test > Reporter: Noah Watkins > Assignee: jay vyas > Fix For: 2.6.0 > > Attachments: HADOOP-11244.patch, HADOOP-11244.patch > > > The test AbstractContractAppendTest::testRenameFileBeingAppended appears to > assert the behavior of renaming a file opened for writing. However, the > assertion "assertPathExists("renamed destination file does not exist", > renamed);" fails because it appears that the file "renamed" is never created > (ostensibly it should be the "target" file that has been renamed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)