[jbosstools-issues] [JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-13411 at 1/23/13 1:01 PM:
-------------------------------------------------------------

[~akazakov]: It's a timeout during a test. Test was trying to unzip Seam runtime to perform some integration test, and the elapsed time for the job run hit 8hrs, so Jenkins killed the thread.

Maybe we can pre-unpack these server runtimes so they're available when tests need them? Perhaps kick off a parallel process at the start of the job which will start the unpacking while everything else is fetching/compiling/resolving? [~mickael_istria], WDYT about running parallel processes during a Tycho build, or running a different job to bootstrap all the runtimes needed by these long-running i-tests?
                
      was (Author: nickboldt):
    [~akazakov]: It's a timeout during a test. Test was trying to unzip Seam runtime to perform some integration test, and the elapsed time for the job run hit 8hrs, so Jenkins killed the thread.
                  
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13411
>                 URL: https://issues.jboss.org/browse/JBIDE-13411
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Visual Page Editor Templates
>    Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Yahor Radtsevich
>            Priority: Blocker
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day,  tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/buildTimeTrend
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.1_trunk.component--javaee/buildTimeTrend
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.integrationtests.aggregate/ ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira