Sorry Greg, totally my mistake in scanning the console log -- I was awestuck, actually -- but I had seen it hanging out there for quite a while; looks like maybe it was stuck on some kind of maven thing. I doubt that many of us are in the habit of checking up on our hudson builds -- that's sort of the whole point of CI. (It looks like Mylyn-Integration is the non-platform long build champion at 2 hr 40 min.)
On Feb 8, 2012, at 2:45 PM, Greg Watson wrote: > Just to be strictly accurate, the last PTP run took 22 minutes, not 22 hours. > In any case, I don't check the hudson page regularly so I had no idea that it > was being shut down and this job was holding things up. An email to this list > would have helped. > > Greg > > On Feb 8, 2012, at 2:42 PM, Ed Willink wrote: > >> Hi Miles >> >> I suspect that the 'longest' job is often a job that is waiting for >> deadlocked broken daemons to magically unlock/time-out. >> >> I know that on a couple of occasions MDT/OCL was one of the blockers even >> though I had explicitly killed the problem jobs. >> >> Regards >> >> Ed >> >> >> On 08/02/2012 18:09, Miles Parker wrote: >>> Hi all, >>> >>> I wanted to bring up a Hudson annoyance and see if people had ideas for >>> improving this. What's happening now is that any time Hudson gets sent a >>> shutdown, everyone is locked out until the last job in queue finishes. >>> Which is a) Good news for the people with running builds, b) Bad news for >>> everyone else. Observing that most of the time most of us are in category >>> b) I vote for making things work better for group b). Nothing against PTP >>> :D, but they happen to be in group a) this time around and the last run >>> took 22 hours. :O But there are lot's of long builds out there. This means >>> that snapshots are delayed for everyone. >>> >>> So I'm wondering if it might be possible to have some kind of policy where >>> builds are terminated with prejudice under shutdown. I'm not sure if a) >>> this is even supportable OOTB in Hudson, and b) whether that would have the >>> possibility of FUBAR'ing anyone project builds. As project builds should >>> not be relying on previous state, I would say that the answer to b is >>> probably no. I also imagine allowance should be made for key builds such as >>> aggregator. IIRC in the past when in release panic mode we were triggering >>> hard shutdowns from time to time. >>> >>> thoughts? >>> >>> Miles >>> _______________________________________________ >>> cross-project-issues-dev mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> >>> >>> ----- >>> No virus found in this message. >>> Checked by AVG - www.avg.com >>> Version: 2012.0.1913 / Virus Database: 2112/4794 - Release Date: 02/07/12 >>> >>> >> >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
