[
https://issues.apache.org/jira/browse/HADOOP-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603247#action_12603247
]
Hadoop QA commented on HADOOP-3491:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12383602/HADOOP-3491-3.patch
against trunk revision 664159.
+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 tests are needed for 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/2612/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2612/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2612/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2612/console
This message is automatically generated.
> Name-node shutdown causes InterruptedException in ResolutionMonitor
> -------------------------------------------------------------------
>
> Key: HADOOP-3491
> URL: https://issues.apache.org/jira/browse/HADOOP-3491
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Konstantin Shvachko
> Assignee: Lohit Vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-3491-1.patch, HADOOP-3491-2.patch,
> HADOOP-3491-3.patch
>
>
> ResolutionMonitor.run() catches a general Exception and logs them no matter
> what.
> It should explicitly catch the InterruptedException and exit gracefully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
