[jbosstools-dev] Test failures/timeout are very bad

[Nick Boldt]

OK, so the net of this conversation is that the Base job should be 
switched back to using Xvnc instead of Xvfb? Should we do the same for 
all the other jobs, or flip them over on a case-by-case basis, only as 
required?

N

On 05/23/2013 02:43 AM, Mickael Istria wrote:
> On 05/23/2013 12:39 AM, Denis Golovin wrote:
>> On 05/22/2013 01:42 PM, Snjezana Peco wrote:
>>> We would need to apply
>>> https://github.com/jbosstools/jbosstools-build/pull/88. See
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=405456
>>> The test failure at
>>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Trunk/job/jbosstools-base_master/260/testReport/org.jboss.tools.common.model.test/ClassPathTest/testSharingJarContent/
>>> is caused by this bug.
>> The real cause of this issue is xvfb started to provide display for
>> tests, switching to xvnc solves the issue. The same problem was
>> discovered for hibernate tests, even disabling workspace auto save job
>> through plugin_customization.ini didn't solve the issue and build stuck
>> anyway in Display.sleep() method forever.
> There is a drawbackt to Xvnc, see
> https://issues.jboss.org/secure/EditComment!default.jspa?id=12470366&commentId=12713633
> .
> Howerver I highly prefer using Xvnc in build (and risking some
> error_code 13) than configuring build in a way that the test instance
> behaves much differently from the actual user workspace.
>
> So -1 for the patch, +1 for Xvnc.
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

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