You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@james.apache.org by Tim Ellison <t....@gmail.com> on 2009/11/09 10:52:17 UTC
[hudson] Killed misbehaving build "james-server-v2.3-m2/489"
Dear James devs,
FYI I just killed a James server build on Hudson that has been running
for ~30hrs and was apparently stuck.
See
http://hudson.zones.apache.org/hudson/job/james-server-v2.3-m2/489/
Regards,
Tim
Re: [hudson] Killed misbehaving build "james-server-v2.3-m2/489"
Posted by Justin Mason <jm...@jmason.org>.
thanks. fwiw, if you find future ones like this, it's worth looking
at their "Configure" page to see if they have a build timeout set;
often they don't, although they are supposed to. A timeout of 2 hours
should take care of 99% of builds.
--j.
On Mon, Nov 9, 2009 at 09:52, Tim Ellison <t....@gmail.com> wrote:
> Dear James devs,
>
> FYI I just killed a James server build on Hudson that has been running
> for ~30hrs and was apparently stuck.
>
> See
> http://hudson.zones.apache.org/hudson/job/james-server-v2.3-m2/489/
>
> Regards,
> Tim
>
>
--
--j.
Re: [hudson] Killed misbehaving build "james-server-v2.3-m2/489"
Posted by Justin Mason <jm...@jmason.org>.
thanks. fwiw, if you find future ones like this, it's worth looking
at their "Configure" page to see if they have a build timeout set;
often they don't, although they are supposed to. A timeout of 2 hours
should take care of 99% of builds.
--j.
On Mon, Nov 9, 2009 at 09:52, Tim Ellison <t....@gmail.com> wrote:
> Dear James devs,
>
> FYI I just killed a James server build on Hudson that has been running
> for ~30hrs and was apparently stuck.
>
> See
> http://hudson.zones.apache.org/hudson/job/james-server-v2.3-m2/489/
>
> Regards,
> Tim
>
>
--
--j.