[
https://issues.apache.org/jira/browse/HDFS-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139940#comment-14139940
]
Hadoop QA commented on HDFS-7049:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12669904/HDFS-7049-branch-2.002.patch
against trunk revision 6434572.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8097//console
This message is automatically generated.
> TestByteRangeInputStream.testPropagatedClose fails and throw NPE on branch-2
> ----------------------------------------------------------------------------
>
> Key: HDFS-7049
> URL: https://issues.apache.org/jira/browse/HDFS-7049
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Juan Yu
> Assignee: Juan Yu
> Priority: Minor
> Attachments: HDFS-7049-branch-2.002.patch, HDFS-7049-branch-2.patch
>
>
> On branch-2, TestByteRangeInputStream.testPropagatedClose throw NPE when
> HftpFileSystem$RangeHeaderUrlOpener.connect
> This is due to fix of HDFS-6143 "WebHdfsFileSystem open should throw
> FileNotFoundException for non-existing paths"
> public ByteRangeInputStream(URLOpener o, URLOpener r) throws IOException {
> this.originalURL = o;
> this.resolvedURL = r;
> getInputStream();
> }
> the getInputStream() will be called in constructor now to verify if file
> exists.
> Since we just try to test if ByteRangeInputStream#close is called at proper
> time, we could mock(ByteRangeInputStream.class, CALLS_REAL_METHODS) for
> testing to avoid the NPE issue.
> I believe the trunk version already does this, we just need to merge the test
> from trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
