[jbosstools-dev] ACTION REQUIRED: Test Failures in JBoss Tools 4.2.0.Alpha1

[Nick Boldt]

With double the time to run (6hrs instead of 3), these jobs are now 
showing test failures instead of build timeout:

*server:*

org.jboss.ide.eclipse.archives.test: Process timeout out after 2400 seconds
org.jboss.ide.eclipse.archives.ui.test: Process timeout out after 2400 
seconds

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-server_42/5/console

*javaee:*

org.jboss.tools.cdi.core.test: Process timeout out after 2400 seconds
org.jboss.tools.jsf.test: Process timeout out after 3600 seconds
org.jboss.tools.jsf.ui.test: Process timeout out after 3600 seconds
org.jboss.tools.seam.core.test: Process timeout out after 1800 seconds
org.jboss.tools.seam.ui.test: Process timeout out after 1800 seconds

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-javaee_42/6/console



On 12/09/2013 03:57 PM, Nick Boldt wrote:
> If your project is listed below, please have a look at your latest
> build(s) and if you can reproduce the problems listed, please fix them
> in your master branch. There's no need to backport these to the Alpha1x
> branch unless they expose a real underlying blocker issue for which your
> project is entirely broken.
>
> These may be fixable by adding more time to the tests' pom.xml files (if
> it's a simple timeout due to network connectivity or some other process
> that takes longer on Jenkins than when you build locally) or else you
> might need to check for blocking UI or threads (in which case, no
> additional time will help as it's a flaw in the test).
>
> Note that for jobs that fail due to overall job timeout (server,
> javaee), I've doubled the timeout to 6hrs (360 mins).
>
> But really, should your component take more than 3hrs to build & run
> tests? Maybe some of those long-running tests should be moved to the
> integration tests project?
>
> [1]
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/tests
>
>
> ----
>
> *webservices:*
>
> org.jboss.tools.ws.creation.core.test: Process timeout out after 3600
> seconds
>
> *vpe:*
>
> Unstable (yellow) due to 1 test failure in
> org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent
>
>
> *server:*
>
> Build timed out (after 180 minutes) while testing. Some tests did not run.
>
> *jst:*
>
> org.jboss.tools.jst.web.kb.test: Process timeout out after 2400 seconds
> org.jboss.tools.jst.web.test: Process timeout out after 2400 seconds
> org.jboss.tools.jst.web.ui.test: Process timeout out after 2400 seconds
>
> *javaee:*
>
> Build timed out (after 180 minutes) while testing. Some tests did not run.
>
> *hibernate:*
>
> org.jboss.tools.hibernate.jpt.core.test: Process timeout out after 2400
> seconds
>
> *central (maven):*
>
> org.jboss.tools.maven.sourcelookup.test: Process timeout out after 2400
> seconds
>
> *base:*
>
> org.jboss.tools.common.model.test: Process timeout out after 2400 seconds
>
> *aerogear:*
>
> job misconfig (wrong path to all-tests/pom.xml), should be fixed now.
> respinning.
>
>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com