[jbosstools-issues] [JBoss JIRA] (JBIDE-21630) itest timeout not respected

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-21630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-21630:
-------------------------------
    Attachment: jbide21630-tests.png


> 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.4.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>              Labels: help_wanted
>             Fix For: 4.4.0.Alpha1
>
>         Attachments: jbide21630-tests.png, jbide21630.png
>
>
> 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#L57-L58
> 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/DevStudio_Master/job/jbosstools-server_master/910/console
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)