[CONTINUUM-667] need a way to limit the mount of time a unit test runs for

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.3
• Fix Version/s: 1.1-alpha-1
• Component/s: Core system, Web interface
• Assignee: kenneyw
• Reporter: James Strachan
• Created: 27/Apr/06 11:12
• Updated: 15/Sep/06 05:34
• Resolved: 15/Sep/06 05:34

Description

We get lots of builds hanging in CI due to test cases with timing issues on different platforms. (You'd be amazed how easy that is to do). We need a way to put in a maximum amount of time (say 5 minutes) for a single unit test - or a max time per entire test run (say 1 hour) so that we can be alerted if a test hangs.

If a test hangs it normally hoses the entire CI server. The worst thing is this makes the entire CI useless since it does no more builds and we don't know its failed.

I understand there are complications in killing stuff in Java. (Though java.lang.Process.destroy() works for most things). One option is to just have a status XML file we can poll for on a canoncial URL

http;//serverhost/module/status.xml

then we can look to see if any of the builds are blocked and if they are we can get nagios or something to reboot the box / restart the CI server etc.

Issue Links

• is duplicated by: CONTINUUM-669 Ability to set timeout to a build
• is related to: CONTINUUM-369 Stop button to cancel the "in progress" of a project.