[
https://issues.apache.org/jira/browse/HDFS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022579#comment-13022579
]
Matt Foley commented on HDFS-1829:
----------------------------------
Cos, this patch only modifies TestNodeCount, and TestNodeCount and its methods
are not called from outside that unit test module, so other tests failing have
nothing to do with this test. However, I am waiting for another run of Hudson
and will respond to its results before asking for a commit. Thanks.
> TestNodeCount waits forever, errs without giving information
> ------------------------------------------------------------
>
> Key: HDFS-1829
> URL: https://issues.apache.org/jira/browse/HDFS-1829
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Matt Foley
> Assignee: Matt Foley
> Fix For: 0.23.0
>
> Attachments: 1829_TestNodeCount_v4.patch, TestNodeCount.java.patch,
> TestNodeCount_v2.patch
>
>
> In three locations in the code, TestNodeCount waits forever on a condition.
> Failures result in Hudson/Jenkins "Timeout occurred" error message with no
> information about where or why. Need to replace with TimeoutExceptions that
> throw a stack trace and useful info about the failure mode.
> Also investigate possible cause of failure.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
