hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-7081) QA bot doesn't post to JIRA if build times out
Date Fri, 31 Dec 2010 18:38:46 GMT

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

Todd Lipcon commented on HADOOP-7081:
-------------------------------------

Setting up something like this would be really nice:
http://www.attivio.com/blog/56-java-development/379-enhancing-junit-with-default-timeouts-and-stack-traces.html

It seems since we run junit in fork mode we could just System.exit(1) after dumping stacks

> QA bot doesn't post to JIRA if build times out
> ----------------------------------------------
>
>                 Key: HADOOP-7081
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7081
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test
>            Reporter: Todd Lipcon
>            Priority: Minor
>
> Currently there are some HDFS tests that time out and deadlock trying to exit. When this
happens, the QA bot builds time out and doesn't post anything to the issue. See for example:
> https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/55/console
> We could either fix the QA bot somehow, or preferably, is there a JUnit runner we can
use that will kill -9 the forked JVM if it deadlocks trying to exit?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message