Re: [xtext-dev] [WARNING / 201 W] TMF XTEXT HEAD Build 0.7.0 / N20090204

[Nick Boldt <nickboldt@xxxxxxxxx>]

Built in delays are dangerous because you're on different (virtual) 
hardware than you run locally. And because it's a shared server, your 
build's priority can flip around around while others are using the box. 
It's not uncommon for emft.eclipse.org to be running several builds at once.

Can you make your tests key on responses to input rather than timeouts? 
Or set a longer timeout? Or some listener to shut down the test if it's 
been stuck for more than X minutes?

Or, if you have any insights into why we can't run UI tests on 
modeling.eclipse.org, we can work to get *that* fixed and you can run 
your build there, where it's faster and there's more space (disc + RAM).

https://bugs.eclipse.org/bugs/show_bug.cgi?id=253114

As to JUnit4...

https://bugs.eclipse.org/bugs/show_bug.cgi?id=153429

Peter Friese wrote:
> > The Xtext tests do work now, except for the UI tests which always 
> > cause the build to hang. Any idea why?
>
> I had a look at the JUnit test results, but couldn't find any evidence 
> for the UI test whatsoever. Could you please point out where I need to 
> look in order to see whether they hang or not? We have some built-in 
> delays in the UI tests, those might be the reason for hanging.
>
> Peter
> _______________________________________________
> xtext-dev mailing list
> xtext-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/xtext-dev

--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb