Re: [jbosstools-dev] Fwd: Build failed in Jenkins: jbosstools-javaee_master #541
Nick,
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.
/Victor
On 02/05/2014 07:36 PM, Nick Boldt wrote:
You can extend the timeout provided to individual tests if they
require
more time (pom.xml), or you can extend the timeout for the whole job
(Jenkins).
Here's an example of how to add more time to a test plugin:
https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org....
If you need that a job be given more time to run, just edit your job
directly to increase the timeout, or ask Mickael or myself and we can
make the change for you.
Cheers,
Nick
On 02/04/2014 03:25 AM, Mickael Istria wrote:
> On 02/04/2014 12:44 AM, Denis Golovin wrote:
>> It is maven or surefire killing timed out process, not jenkins.
> Right, and as far as I know Surefire doesn't provide hooks. So I don't
> know a good way to make you happy with that.
> I have some SSH and VPN access to the Jenkins slave. In case you notice
> one slave is in trouble, feel free to ask me, I'll connect and run
> jstack or whatever helps you to figure out the cause of the issue.
> --
> 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
>