[ http://jira.codehaus.org/browse/CONTINUUM-667?page=all ]
Emmanuel Venisse updated CONTINUUM-667:
---------------------------------------
Fix Version: 1.1
> need a way to limit the mount of time a unit test runs for
> ----------------------------------------------------------
>
> Key: CONTINUUM-667
> URL: http://jira.codehaus.org/browse/CONTINUUM-667
> Project: Continuum
> Type: Bug
> Components: Web interface, Core system
> Versions: 1.0.3
> Reporter: james strachan
> Priority: Blocker
> Fix For: 1.1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
