Hopefully most of the IO errors are gone now. I've closed the ticket
https://code.ros.org/trac/ros/ticket/3736
Our proxy server was overwhelmed, and that was why pip and apt-get were
failing in the bootstrap stages. If you do see these errors in Electric
please do ticket them like Bhaskara did. Otherwise we won't keep track of
them well enough, and we may have a bigger problem than we know.
Also to help get visibility into trends on hudson I have setup mailing
lists to archive the results of tests. If you want to see the status of
recent devel builds see the archives of
https://kforge.ros.org/rosrelease/devel and for prereleases see
https://kforge.ros.org/rosrelease/prerelease
Note there are still some major issues with Oneiric in unstable distro
which will get these sort of errors.
Thanks for the patience,
Tully
On Wed, Nov 9, 2011 at 10:42 AM, Wim Meeussen <
meeussen@willowgarage.com>wrote:
> > I've been seeing such errors as well, with prerelease builds, and
> > filed a ticket at https://code.ros.org/trac/ros/ticket/3736. One
> > thing I noticed from the errors was that a pip install step often
> > seemed to be failing.
>
> This is a problem in the boostrap process, and affects all Hudson builds.
>
> For the devel builds, I created another ticket that covers some
> failure cases that can occur after the boostrap:
>
> https://code.ros.org/trac/ros/ticket/3744
>
>
> Wim
>
>
> --
> --
> Wim Meeussen
> Willow Garage Inc.
> <http://www.willowgarage.com)
> _______________________________________________
> Ros-release mailing list
> Ros-release@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-release
>
--
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote@willowgarage.com
(650) 475-2827
(text/plain)