maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-667) need a way to limit the mount of time a unit test runs for
Date Thu, 27 Apr 2006 16:17:21 GMT
    [ ] 

james strachan commented on CONTINUUM-667:

Incidentally just knowing that there is a blocked build would mean we can reboot the CI servers
every night and mail folks with details of the test that blocked.

(BTW knowing the test which hung would be very useful in the XML doc)

> need a way to limit the mount of time a unit test runs for
> ----------------------------------------------------------
>          Key: CONTINUUM-667
>          URL:
>      Project: Continuum
>         Type: Bug

>   Components: Web interface, Core system
>     Versions: 1.0.3
>     Reporter: james strachan
>     Priority: Blocker

> 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:
For more information on JIRA, see:

View raw message