Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348943 - Virgo (and others?) need to specify "timeout" for Hudson build jobs.
Summary: Virgo (and others?) need to specify "timeout" for Hudson build jobs.
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Cross-Project (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Cross-Project issues CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-09 14:53 EDT by David Williams CLA
Modified: 2011-08-31 23:56 EDT (History)
1 user (show)

See Also:

Attachments
screen shot showing long running jobs (12.02 KB, image/png)
2011-06-09 14:54 EDT, David Williams CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 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 CLA 2011-06-09 14:54:27 EDT 
Created attachment 197721 [details]
screen shot showing long running jobs
Comment 2 David Williams CLA 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.