[jbosstools-dev] ACTION REQUIRED: Test failures in 4.3.x branch for JavaEE, JST, Openshift, and Server

[André Dietisheim]

As for OpenShift this is again the misterious EGit testing-zombie at 
work that keeps appearing and disappearing at times and only occurrs in 
jenkins.
When this started to happen back in July the pattern was that it 
appeared on virt-machines only which I solved back then with an 
exclusion pattern for slaves: https://issues.jboss.org/browse/JBIDE-20389
I hit the trigger again (without any changes) and OpenShift is back on blue.
I suspect my slave exclusion pattern isnt safe since I now see *virt* 
servers running the tests again.

On 11/04/2015 07:14 PM, Nick Boldt wrote:
> Please fix your tests, or I'll be forced to open JIRAs and ask you to
> fix your tests again. :D
>
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-server_4.3.mars/
> (5 tests)
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/
> (2 tests)
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-jst_4.3.mars/
> (2 tests)
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-javaee_4.3.mars/
> (1 test)
>
> If your tests are intermittently failing, please consider them as
> tests you shouldn't run as part of your automated Jenkins test suite.
> Maybe they should be moved to an integration tests suite, or only run
> locally via some -Pwonky-tests profile. If you would like assistance /
> PR to move tests out of your default suite and into a separate one, so
> that you can consistently have blue balls for all builds, let me know
> and I'll be happy to help.
>
> Cheers,
>
> Nick
>