[
https://issues.apache.org/jira/browse/HADOOP-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794418#action_12794418
]
Hadoop QA commented on HADOOP-6220:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12428910/HADOOP-6220.patch
against trunk revision 893666.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/237/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/237/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/237/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/237/console
This message is automatically generated.
> HttpServer wraps InterruptedExceptions by IOExceptions if interrupted in
> startup
> --------------------------------------------------------------------------------
>
> Key: HADOOP-6220
> URL: https://issues.apache.org/jira/browse/HADOOP-6220
> Project: Hadoop Common
> Issue Type: Bug
> Components: util
> Affects Versions: 0.21.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: HADOOP-6220.patch
>
>
> Following on some discusson on mapred-dev, we should keep an eye on the fact
> that Jetty uses sleeps when starting up; jetty can be a big part of the
> delays of bringing up a node. When interrupted, the exception is wrapped by
> an IOException, the root cause is still there, just hidden.
> If we want callers to distinguish InterruptedExceptions from IOEs, then this
> exception should be extracted. Some helper method to start an http daemon
> could do this -catch the IOE, and if there is a nested interrupted exception,
> rethrow it, otherwise rethrowing the original IOE
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
