[
https://issues.apache.org/jira/browse/HADOOP-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190351#comment-14190351
]
Steve Loughran commented on HADOOP-11244:
-----------------------------------------
# need to understand why the raw local tests aren't running first, because they
should -and this problem should have surfaced. if they aren't running, we don't
catch regressions
# what happens to all the other filesystems with this test. I'd expect the
object stores to fail because they cache the destination on output stream
creation, and only write on close().
if we are getting inconsistent outcomes, this will have to become one of those
fs switch things.
> 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
>
>
> 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)
