On Thu, Nov 21, 2013 at 6:25 PM, Isaac Isao Saito <
iisaito@opensource-robotics.tokyo.jp> wrote:
> Thank you Tully, now I see all green at least with my packages. Let me
> still ask one thing more,
>
> On Fri, Nov 22, 2013 at 2:53 AM, Tully Foote <tfoote@osrfoundation.org>
> wrote:
> > :
> > The one you linked to has a broken upstream dependency.
> >
> > Which looking at that it appears that one of the slaves went offline:
>
> Is the cause of a slave going offline in one or some of the packages
> in the build chain? If so, do you have an idea what can potentially
> cause it? Sorry, this may be a pure jenkins question, but I couldn't
> find a reasonable answer after googling..
>
It's just generally the machine malfunctions. Sometimes they lose
connectivity, run out of disk or memory space, etc. They're running for
weeks to months sometimes continuously busy. If they crash cleanly jenkins
will just skip them. If they still accept jobs but fail due to underlying
problems you see the errors.
Tully
>
> Isaac
>
> --
> !Happy opensource robotics!
>
> Isao Isaac Saito (齋藤功)
> Software Engineer, Co-founder
> TORK (Tokyo Opensource Robotics Kyokai Association, 東京オープンソースロボティクス協会)
> http://opensource-robotics.tokyo.jp
>
>
> On Fri, Nov 22, 2013 at 2:53 AM, Tully Foote <tfoote@osrfoundation.org>
> wrote:
> > Hi Isaac,
> >
> > The one you linked to has a broken upstream dependency.
> >
> > Which looking at that it appears that one of the slaves went offline:
> >
> http://jenkins.ros.org/view/HbinP64/job/ros-hydro-hironx-ros-bridge_binarydeb_precise_amd64/2/console
> >
> > I've taken that slave offline and am debugging what went wrong. And I've
> > triggered all the red jobs with valid upstream dependencies which should
> > clean up the spurrious failures.
> >
> > Tully
> >
> >
> > On Thu, Nov 21, 2013 at 12:54 AM, Isaac Isao Saito
> > <iisaito@opensource-robotics.tokyo.jp> wrote:
> >>
> >> ROS releasers,
> >>
> >> # I'm not sure if I should've asked on ros-builders or else.
> >>
> >> Since a few days ago, maybe after Nov 18 US time, I've started getting
> >> failure notice from buildfarm, even for the packages of the version
> >> that used to build.
> >>
> >> Example:
> >>
> http://jenkins.ros.org/view/HbinP64/job/ros-hydro-nextage-ros-bridge_binarydeb_precise_amd64/4/console
> >>
> >> Looks like it's not just ours:
> >> http://www.ros.org/debbuild/hydro.html?q=red
> >>
> >> Is it just a temporary glitch / key upstream dependencies failing /
> >> has jenkins script updated so that it now detects errors that were not
> >> covered before?
> >>
> >> Thanks!
> >>
> >> --
> >> !Happy opensource robotics!
> >>
> >> Isao Isaac Saito (齋藤功)
> >> Software Engineer, Co-founder
> >> TORK (Tokyo Opensource Robotics Kyokai Association, 東京オープンソースロボティクス協会)
> >> http://opensource-robotics.tokyo.jp
> >> _______________________________________________
> >> ros-release mailing list
> >> ros-release@code.ros.org
> >> http://lists.ros.org/mailman/listinfo/ros-release
> >
> >
> _______________________________________________
> ros-release mailing list
> ros-release@code.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
(text/plain)