[
https://jira.codehaus.org/browse/CONTINUUM-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277074#comment-277074
]
Maria Catherine Tan commented on CONTINUUM-2656:
------------------------------------------------
I think what we can do for here is to have a worker that will constantly checks
if the builds are still active. If they are not active but state is still
updating/building, then we assume that there must be some problem with the
agent for it not to return the build result and then stops the build.
> Distributed build may never return
> ----------------------------------
>
> Key: CONTINUUM-2656
> URL: https://jira.codehaus.org/browse/CONTINUUM-2656
> Project: Continuum
> Issue Type: Bug
> Components: Distributed Builds
> Affects Versions: 1.4.1 (Beta)
> Reporter: Brett Porter
> Assignee: Maria Catherine Tan
>
> Under the circumstances outlined in CONTINUUM-2655, the build result is never
> returned to the server. In this case, the server never times out waiting for
> the response, and further pings do not encourage the agent to present the
> failure.
> The build will run forever if it was forced and not respecting the timeout
> value. It can no longer be cancelled as it doesn't appear in the queue.
> Two things are needed:
> - A failure to respond should generate a new error response (with a simpler
> message less likely to fail)
> - The server should check for a lack of response and end the build if the job
> has finished
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
