www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Toulme <anto...@lunar-ocean.com>
Subject Re: Mahout builds
Date Tue, 24 Aug 2010 22:14:04 GMT
+1

On Tue, Aug 24, 2010 at 15:13, sebb <sebbaz@gmail.com> wrote:

> On 24 August 2010 21:36, Antoine Toulme <antoine@lunar-ocean.com> wrote:
> > I discussed with the kind folks in #hudson. In both cases, the build is
> > killed.
> > If the button is checked, the build will show as failed (red ball),
> > otherwise it will be blank (white/grey ball).
>
> In that case the "fail" help could do with updating. It says:
>
> "If checked, the build will be failed rather than aborted."
>
> That could easily mean that the build will not be aborted at all.
>
> I'll see about raising a bug report.
>
> > So it's up to projects to consider builds that take too long as failures.
> > For Buildr I consider a build that goes over the timeout to be a failed
> > build for example.
> >
> > On Tue, Aug 24, 2010 at 12:18, Niklas Gustavsson <niklas@protocol7.com
> >wrote:
> >
> >> On Tue, Aug 24, 2010 at 5:47 PM, Antoine Toulme <
> antoine@lunar-ocean.com>
> >> wrote:
> >> > Two mahout builds were taking over vesta.
> >> >
> >> > I killed both, and checked that they both have timeouts.
> >> > They both have one, but they don't have the checkbox "Fail the build"
> >> under
> >> > it checked.
> >> >
> >> > It looks like to my eyes this checkbox is necessary to kill the build
> and
> >> > stop recording stuff.
> >>
> >> While I would have agreed with your interpretation. However, as
> >> mentioned by sebb, the checkbox needs to be unchecked. Else, Hudson
> >> will only fail the build, not attempt to kill it.
> >>
> >> Sometimes, even with the build timeout, Hudson fails to kill stuck
> >> builds. One reason seems to be when the socket to a slave is broken.
> >>
> >> /niklas
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message