Guys, it looks like I was wrong about
maven killing the process. In my local builds when it fails
because of time out eclipse keeps still running. So it could be
jenkins killing leftover processes fro job.
On 02/05/2014 12:23 PM, Mickael Istria wrote:
On 02/05/2014 04:46 PM, Victor
Rubezhny wrote:
we don't need to extend the timeout value. We need to get the stacktrace
written into some log-file _before_ the test is killed by the timeout.
Usually the fact of some test is timed out mean some hang up or even a
deadlock occurred, so we need to determine the reason of such a problem
and as such we need to have a stacktrace logged somehow.
So, we are finding a way to run something like 'jstack -F <PID> | tee
<test>/target/work/data/.metadata/jstack.log' or something like this
_right_before_ the test will be killed by surefire as timed out.
Is there a Jira for this request? If not, can you please create
one to carry on this discussion?
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________