[
https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13411 at 7/2/13 9:14 AM:
------------------------------------------------------------
As far as I can tell from stats in Jenkins, the last long build was Jan 31 (>7hrs).
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_master/buildTimeTrend}
Build ↑ Duration Slave
Failed #424 4 hr 23 min dev56-rhel6-x86
Failed #423 3 hr 44 min dev115-rhel5-x86
Failed #422 22 min vmg39-rhel6-x86_64
Failed #421 3 hr 49 min dev115-rhel5-x86
Failed #420 3 hr 44 min dev115-rhel5-x86
Success #417 2 hr 46 min dev115-rhel5-x86 (June 23)
Unstable #404 2 hr 47 min dev115-rhel5-x86 (June 12)
Failed #275 7 hr 22 min dev117-rhel5-x86_64 (Jan 31)
Unstable #238 3 hr 40 min dsp06-rhel5-x86_64 (Jan 14)
Success #226 6 hr 0 min vmg19-rhel5-x86 (Jan 10)
{code}
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/buildTimeTrend}
Failed #89 3 hr 9 min dev109-rhel6-x86_64
Success #88 1 hr 50 min vmg39-rhel6-x86_64 (June 30)
Failed #85 19 min vmg39-rhel6-x86_64
Unstable #82 1 hr 55 min vmg39-rhel6-x86_64 (June 23)
{code}
As we're now running w/ Xvnc, and jobs are taking 2 or 3 hrs instead of 7 or 8 (except
when tests get stalled and it takes over 3.5hrs), we might be OK to close this.
[~mickael_istria], WDYT?
was (Author: nickboldt):
As far as I can tell from stats in Jenkins, the last long build was Jan 31
(>7hrs).
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_master/buildTimeTrend}
Build ↑ Duration Slave
Failed #424 4 hr 23 min dev56-rhel6-x86
Failed #423 3 hr 44 min dev115-rhel5-x86
Failed #422 22 min vmg39-rhel6-x86_64
Failed #421 3 hr 49 min dev115-rhel5-x86
Failed #420 3 hr 44 min dev115-rhel5-x86
Success #417 2 hr 46 min dev115-rhel5-x86 (June 23)
Unstable #404 2 hr 47 min dev115-rhel5-x86 (June 12)
Failed #275 7 hr 22 min dev117-rhel5-x86_64 (Jan 31)
Unstable #238 3 hr 40 min dsp06-rhel5-x86_64 (Jan 14)
Success #226 6 hr 0 min vmg19-rhel5-x86 (Jan 10)
{code}
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/buildTimeTrend}
Failed #89 3 hr 9 min dev109-rhel6-x86_64
Success #88 1 hr 50 min vmg39-rhel6-x86_64 (June 30)
Aborted #87 11 sec vmg39-rhel6-x86_64
Aborted #86 6.3 sec vmg39-rhel6-x86_64
Failed #85 19 min vmg39-rhel6-x86_64
Unstable #82 1 hr 55 min vmg39-rhel6-x86_64 (June 23)
{code}
As we're now running w/ Xvnc, and jobs are taking 2 or 3 hrs instead of 7 or 8 (except
when tests get stalled and it takes over 3.5hrs), we might be OK to close this.
[~mickael_istria], WDYT?
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.2.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/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
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...
?
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