[
https://issues.apache.org/jira/browse/LUCENE-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485491#comment-13485491
]
Dawid Weiss commented on LUCENE-4510:
-------------------------------------
This is trickier than I thought. The problem is that heartbeats are in fact
generated on the master side (not on the forked JVM) based on the activity in
the event stream for a particular forked JVM (that's why it was possible to
generate a heartbeat from an "unknown" location in the test execution
timeline). The naming is confusing here, blame me.
To generate a stack trace of the forked JVM we'd need to do it remotely (and
know its PID) or do it locally (and propagate it back to the master). This
isn't a trivial refactoring, I'll need some time to do it. In the mean time
I'll release the fix for the shutdown hooks issue -- this should help in
getting those stalled runs to complete (with a suite timeout on forked JVMs and
corresponding stack traces).
> when a test's heart beats it should also throw up (dump stack of all threads)
> -----------------------------------------------------------------------------
>
> Key: LUCENE-4510
> URL: https://issues.apache.org/jira/browse/LUCENE-4510
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
>
> We've had numerous cases where tests were hung but the "operator" of that
> particular Jenkins instance struggles to properly get a stack dump for all
> threads and eg accidentally kills the process instead (rather awful that the
> same powerful tool "kill" can be used to get stack traces and to destroy the
> process...).
> Is there some way the test infra could do this for us, eg when it prints the
> HEARTBEAT message?
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
