[
https://issues.apache.org/jira/browse/HDFS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022575#comment-13022575
]
Matt Foley commented on HDFS-1829:
----------------------------------
Eli, can we open another Jira for that? My goal here was only to get rid of
the recurring false positive in Hudson for this unit test, which this patch
does in a clean way. Your suggestion would be a good contribution to the
toolkit (and I have been trying to do that along the way, as you know), but
I've already spent more time than I should on this issue.
> 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
