[
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472337#comment-13472337
]
Hudson commented on HADOOP-8894:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #1190 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1190/])
HADOOP-8894. GenericTestUtils.waitFor should dump thread stacks on timeout.
Contributed by Todd Lipcon. (Revision 1395825)
Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1395825
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/GenericTestUtils.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/TimedOutTestsListener.java
> GenericTestUtils.waitFor should dump thread stacks on timeout
> -------------------------------------------------------------
>
> Key: HADOOP-8894
> URL: https://issues.apache.org/jira/browse/HADOOP-8894
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 3.0.0, 2.0.3-alpha
>
> Attachments: hadoop-8894.txt, hadoop-8894.txt
>
>
> Many tests use this utility to wait for a condition to become true. In the
> event that it times out, we should dump all the thread stack traces, in case
> the timeout was due to a deadlock. This should make it easier to debug
> scenarios like HDFS-4001.
--
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
