[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472394#comment-13472394
 ] 

Hudson commented on HADOOP-8894:


Integrated in Hadoop-Mapreduce-trunk #1221 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1221/])
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


[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-09 Thread Hudson (JIRA)

[ 
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


[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-08 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472064#comment-13472064
 ] 

Hudson commented on HADOOP-8894:


Integrated in Hadoop-Mapreduce-trunk-Commit #2853 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2853/])
HADOOP-8894. GenericTestUtils.waitFor should dump thread stacks on timeout. 
Contributed by Todd Lipcon. (Revision 1395825)

 Result = FAILURE
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


[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-08 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472003#comment-13472003
 ] 

Hudson commented on HADOOP-8894:


Integrated in Hadoop-Common-trunk-Commit #2830 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2830/])
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


[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-08 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472002#comment-13472002
 ] 

Hudson commented on HADOOP-8894:


Integrated in Hadoop-Hdfs-trunk-Commit #2892 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2892/])
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


[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-08 Thread Eli Collins (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471972#comment-13471972
 ] 

Eli Collins commented on HADOOP-8894:
-

+1

> 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
> 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


[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-08 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471911#comment-13471911
 ] 

Hadoop QA commented on HADOOP-8894:
---

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12548308/hadoop-8894.txt
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1576//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1576//console

This message is automatically generated.

> 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
> 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


[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-07 Thread Eli Collins (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471324#comment-13471324
 ] 

Eli Collins commented on HADOOP-8894:
-

In testFailure the printlns to output should be in the conditional, otherwise 
looks great.

> 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
> Attachments: 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


[jira] [Commented] (HADOOP-8894) GenericTestUtils.waitFor should dump thread stacks on timeout

2012-10-05 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470866#comment-13470866
 ] 

Hadoop QA commented on HADOOP-8894:
---

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12548083/hadoop-8894.txt
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1570//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1570//console

This message is automatically generated.

> 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
> Attachments: 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