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?
-Martin
On 5. 2. 2014, at 21:31, Denis Golovin <dgolovin(a)exadel.com> wrote:
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?
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265