You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2011/01/12 07:12:46 UTC

[jira] Commented: (HADOOP-7081) QA bot doesn't post to JIRA if build times out

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

Konstantin Boudnik commented on HADOOP-7081:
--------------------------------------------

I wonder how Maven's Surefire handles times outs? It feels like moving Hadoop to Maven is pretty much imminent which raises the question about ROI of such modification. I agree though that not-having logs when a timeout occurs is annoying to say the least.

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