Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348943

Summary:

Virgo (and others?) need to specify "timeout" for Hudson build jobs.

Product:

Community

Reporter:

David Williams <david_williams>

Component:

Cross-Project

Assignee:

Cross-Project issues <cross-project.inbox>

Status:

RESOLVED NOT_ECLIPSE

QA Contact:

Severity:

minor

Priority:

CC:

webmaster

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
screen shot showing long running jobs	none

Description David Williams

2011-06-09 14:53:34 EDT

I suspect these build jobs (see attached) are not really doing anything after 3 or 4 hours? Feel free to correct me if I'm wrong, that they really do take that long. 

I'm putting on cross-project as a reminder to everyone. And, CC'ing webmasters since at one point, I think they added a time out to all Hudson jobs ... so, wondering if that got "lost" along the way?

Comment 1 David Williams

2011-06-09 14:54:27 EDT

Created attachment 197721 [details]
screen shot showing long running jobs

Comment 2 David Williams

2011-08-31 23:56:56 EDT

I'll close as "not eclipse" since, if I'm remembering mailing lists correctly, cases like this did turn out to have timeout set, but our dear hudson was not working well enough to "see" them. Or, hung while trying to shut them down. Or something. Only cure was apparently are slave restart ... again, if I am remembering right.