Looks like common behavior of surefire. I see that eclipse instance
still running after it's "killed" by timeout too.
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'.)
/Victor
On 02/06/2014 03:39 PM, Mickael Istria wrote:
On 02/06/2014 12:29 PM, Martin Malina wrote:
> Good you mention this, Denis. We noticed this too - when a test times
> out because of surefire timeout, the job fails, but eclipse keeps
> running on the slave - at least that's the (unfortunate) behavior on
> our local jenkinse instance. Does the Boston jenkins have some plugin
> installed to prevent this? Nick, do you know?
You should open a bug against Tycho to mention it. Timeout is expected
to kill the process under test, it it doesn't, it's a bug in Surefire.
Please open it ASAP and make me a CC.
--
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>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev