]
Nick Boldt updated JBIDE-21630:
-------------------------------
Fix Version/s: 4.3.1.CR1
itest timeout not respected
---------------------------
Key: JBIDE-21630
URL:
https://issues.jboss.org/browse/JBIDE-21630
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, server
Affects Versions: 4.3.1.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 4.3.1.CR1
Server itests are running with a timeout of 2400s, which is the default set in our parent
pom [1].
[1]
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
But the server root pom sets a timeout of 3000s [2], which is being ignored [3]:
[2]
https://github.com/jbosstools/jbosstools-server/blob/master/pom.xml#L17-L18
{code}
13:39:42 [ERROR] Timeout 2400 s exceeded. Process was killed.
{code}
[3]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
So... how can we ensure that the itests get more time to run, so that these extra tests
can be run without crashing? Currently, server is showing 2829 tests, but the last time it
was blue, we had 3434 tests, so there are about 600 tests for which no results are being
logged due to the timeout.