continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-2656) Distributed build may never return
Date Fri, 26 Aug 2011 01:19:34 GMT

    [ https://jira.codehaus.org/browse/CONTINUUM-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277078#comment-277078
] 

Brett Porter commented on CONTINUUM-2656:
-----------------------------------------

How is the queue populated at the moment? I notice that is correct so must be querying the
agents - I would assume this does the same thing.

I'd also like the cancel button on the build to note the build already ended and also be able
to clean it up when pressed instead of waiting for the background job.

> 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

        

Mime
View raw message