[Ros-release] Are pre-release tests supported for dry stacks on Groovy?

[Tully Foote]

Hi Jack,

Our goal is to have the prereleases working correctly.  We're doing our
best to keep the prereleases current with the changes.  It sounds like
we've fallen a step behind on the tests.  We'll see what we can do in the
morning.

As Stephane mentioned the current prereleases are running on the old
buildfarm and they're showing their age.  If you seem to get issues not
releated to your stack retriggering once might be worth it.  But also do
let us know that you're having trouble here and we can try to debug it. We
have been developing new prerelease infrastructure to deploy on the new
farm(or let you run it locally), but it's not ready yet.

Tully

On Sun, Oct 14, 2012 at 3:50 PM, Stéphane Magnenat <
stephane.magnenat at mavt.ethz.ch> wrote:

> I have encountered the same problem while doing the groovy pre-release
> test of ethzasl_message_transport. My understanding is that the pre-release
> farm is running on an old cluster and is in a somewhat shaky state. I have
> also encountered funny errors like "Too many open files" and others,
> clearly not linked to my stack.
>
> I unfortunately have no useful advise on how to work-around this problem,
> I can just say that you are not alone.
>
> Kind regards,
>
> Stéphane
>
> --
> Dr Stéphane Magnenat
> http://stephane.magnenat.net
>
> ______________________________**_________________
> Ros-release mailing list
> Ros-release at code.ros.org
> https://code.ros.org/mailman/**listinfo/ros-release<https://code.ros.org/mailman/listinfo/ros-release>
>



-- 
Tully Foote
tfoote at willowgarage.com
(650) 475-2827
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20121014/6937f2af/attachment-0009.html>