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?