On 02/06/2014 01:09 PM, Victor Rubezhny wrote:
Looks like common behavior of surefire. I see that eclipse instance
still running after it's "killed" by timeout too.
I think it's a
bug. I opened this for discussion
https://bugs.eclipse.org/bugs/show_bug.cgi?id=427556
Currently, the surefire process probably gets killed when its parent
process (Maven) ends.
can we use it to obtain a stacktrace for such a "killed"
eclipse
process? (I'm doing it locally, but here I'm free to get it's PID and
run 'jstack -F PID'.)
Please put this request in a bug. It's not an
easy thing.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>