[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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-13411:
----------------------------------------

[~maxandersen]
> If you can run the same tests in 1/6th of the time outside of tycho resolving target platform

I'm not sure that assumption of "run the same test in 1/6th of the time outside of Tycho resolving target platform" is true. What takes time in Java EE job is test execution, not Tycho. I let you give a try locally and see how much time a "mvn clean verify -Dmaven.test.skip=true" takes, it'll be ~20 minutes, whereas we're speaking of hours here.

> why do you keep saying it is not interesting to have a way to run already built tests run against an installed eclipse ? 

Like they say on Wikipedia: "Quotation needed" ;) I think I never said that.
However, I already said several times that we already have a way to run existing tests against an installed Eclipse. It's just a matter of you telling us what do you want to test against which version of Eclipse and we'll set up the job. Open dedicated Jiras for that.
                
> 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: Build/Releng, Visual Page Editor Templates
>    Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Denis Golovin
>            Priority: Blocker
>             Fix For: 4.1.x
>
>         Attachments: tests-vs-tycho-build-time.png
>
>
> 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