[
https://issues.apache.org/jira/browse/HADOOP-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525221
]
Nigel Daley commented on HADOOP-1831:
-------------------------------------
An RFE has been filed with Hudson:
https://hudson.dev.java.net/issues/show_bug.cgi?id=789
But I think the problem is with Junit. JUnit is *supposed* to timeout a test
if it is taking longer than 15 minutes. This doesn't seem to work reliably if
a test gets really 'wedged'.
Note too that having Hudson timeout a patch build won't have the effect you
desire. It will simply hang the patch queue since the 'current' link on the
filesystem to the patch being tested won't get removed.
> Hudson should kill long running tests
> -------------------------------------
>
> Key: HADOOP-1831
> URL: https://issues.apache.org/jira/browse/HADOOP-1831
> Project: Hadoop
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.15.0
> Reporter: Jim Kellerman
> Fix For: 0.15.0
>
>
> Hudson should kill long running tests. (I believe it is supposed to but
> doesn't quite seem to do the job if the test is really hung up).
> It would be nice if, when the timer goes off, Hudson did a {code}kill
> -QUIT{code} (to try to get a thread dump) and then followed that with a
> {code}kill -9{code}
> (See the section "Killing a hung test" at
> http://wiki.apache.org/lucene-hadoop/HudsonBuildServer )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
