Re: Hudson builds stuck: Tuscany-2x and CXF-Trunk-JDK16
Hi, Another Tuscany-2x build [1] was stuck with lots of OOM errors and other failures in the console log. I killed the build as it was taking already almost 7 hours, which is much more than the 40 minutes used by the last successful build. [1] http://hudson.zones.apache.org/hudson/job/Tuscany-2x/116/ BR, Jukka Zitting
Re: Hudson builds stuck: Tuscany-2x and CXF-Trunk-JDK16
On 30/06/2009, Jukka Zitting wrote: > Hi, > > Another Tuscany-2x build [1] was stuck with lots of OOM errors and > other failures in the console log. I killed the build as it was taking > already almost 7 hours, which is much more than the 40 minutes used by > the last successful build. > > [1] http://hudson.zones.apache.org/hudson/job/Tuscany-2x/116/ It looked to me as though the build was stalled, i.e. Hudson was not able to detect/recover from the situation. Is this a known problem? Is there any way to give the builds a bit more memory? It looks like Tuscany has not built successfully for a long while, so this is likely to keep happening. It's a pity that the console output does not have time-stamps, or it would be a lot easier to tell that nothing was happening. > BR, > > > Jukka Zitting >
Re: Hudson builds stuck: Tuscany-2x and CXF-Trunk-JDK16
On Tue, Jun 30, 2009 at 13:46, sebb wrote: > On 30/06/2009, Jukka Zitting wrote: >> Hi, >> >> Another Tuscany-2x build [1] was stuck with lots of OOM errors and >> other failures in the console log. I killed the build as it was taking >> already almost 7 hours, which is much more than the 40 minutes used by >> the last successful build. >> >> [1] http://hudson.zones.apache.org/hudson/job/Tuscany-2x/116/ > > It looked to me as though the build was stalled, i.e. Hudson was not > able to detect/recover from the situation. Is this a known problem? > > Is there any way to give the builds a bit more memory? > > It looks like Tuscany has not built successfully for a long while, so > this is likely to keep happening. > > It's a pity that the console output does not have time-stamps, or it > would be a lot easier to tell that nothing was happening. It could be the entire machine was under memory pressure, given those OOM errors. I wonder if that caused the Hudson master to get confused. --j.
