[jbosstools-issues] [JBoss JIRA] (JBIDE-18818) Test timeout in org.jboss.tools.jsf.verification.test

[Alexey Kazakov (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022493#comment-13022493 ] 

Alexey Kazakov commented on JBIDE-18818:
----------------------------------------

[~nickboldt], the list of such tests is too long. The problem is not in particular tests but rather in the approach we use in our tests. We need to continue to investigate these problems and also we need to separate integration tests.
Can Jenkins or whatever provide a stacktrace for JVM just before stop the build by timeout? It would be very helpful.

> Test timeout in org.jboss.tools.jsf.verification.test
> -----------------------------------------------------
>
>                 Key: JBIDE-18818
>                 URL: https://issues.jboss.org/browse/JBIDE-18818
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsf
>    Affects Versions: 4.2.1.CR1
>            Reporter: Nick Boldt
>            Assignee: Alexey Kazakov
>            Priority: Blocker
>             Fix For: 4.2.1.Final
>
>
> Tests that time out due to blocking UI or other thread lock result in builds that are recorded as ABORTED [0]. This isn't a problem in terms of publishing new content because the build runs quickly, publishes the new bits, and THEN starts running tests. 
> [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.2.luna/buildTimeTrend
> But where it IS a problem is where we use a buildflow job to run the whole stack of JBT projects. Buildflows will also abort if they encounter an aborted job [1].
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow_4.2.luna/
> Why is this a problem? Because when we do a weekend spin (or respin) not all the projects in the stack are guaranteed to rebuild to verify all the downstream component tests all still work.
> --
> If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move them such that they can still be run LOCALLY using a profile, but will be skipped in Jenkins.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)