[
https://issues.apache.org/jira/browse/HDFS-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486941#comment-13486941
]
Hadoop QA commented on HDFS-4013:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12551345/hdfs-4013.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 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/3426//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3426//console
This message is automatically generated.
> TestHftpURLTimeouts throws NPE
> ------------------------------
>
> Key: HDFS-4013
> URL: https://issues.apache.org/jira/browse/HDFS-4013
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Environment: java version "1.7.0_06-icedtea"
> OpenJDK Runtime Environment (fedora-2.3.1.fc17.2-i386)
> OpenJDK Client VM (build 23.2-b09, mixed mode)
> Reporter: Chao Shi
> Assignee: Chao Shi
> Priority: Trivial
> Attachments: hdfs-4013.patch, hdfs-4013.patch, hdfs-4013.patch
>
>
> The case fails at line 116, where message is null. I guess this may be an
> openjdk-specific behavior, but it would be nice to have it fixed although
> openjdk is not officially supported.
> FYI: The exception is thrown with null message at java.net.SocksSocketImpl.
> {code}
> private static int remainingMillis(long deadlineMillis) throws
> IOException {
> if (deadlineMillis == 0L)
> return 0;
> final long remaining = deadlineMillis - System.currentTimeMillis();
> if (remaining > 0)
> return (int) remaining;
> throw new SocketTimeoutException();
> }
> {code}
--
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
