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).
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 <nik...@protocol7.com>wrote: > On Tue, Aug 24, 2010 at 5:47 PM, Antoine Toulme <anto...@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 >
