You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by sebb <se...@gmail.com> on 2014/07/01 13:47:19 UTC
Re: Continuum appears to have got stuck
On 30 June 2014 02:57, Brett Porter <br...@apache.org> wrote:
> From 2014-06-29 17:46:36 to 17:48:00 UTC, all the builds had this error:
>
> svn: OPTIONS of 'http://svn.apache.org/repos/asf/commons/proper/codec/trunk': could not connect to server (http://svn.apache.org)
>
> Looks like the connection was ok when the next hourly schedule rolled around.
>
> I don't see any error for Directory, so maybe that particular one hung trying to connect giving you what you saw.
Is there any way to add a timeout to the connection?
> - Brett
>
> On 30 Jun 2014, at 4:48 am, sebb <se...@gmail.com> wrote:
>
>> Looks like someone has kicked it into life again - thanks!
>>
>> On 29 June 2014 18:24, sebb <se...@gmail.com> wrote:
>>> Continuum seems to be stuck trying to prepare the build for Directory.
>>> It has been in that state for an hour or more.
>>>
>>> Please could someone have a look?
>>>
>>> Thanks!
>
Re: Continuum appears to have got stuck
Posted by Brett Porter <br...@apache.org>.
On 1 Jul 2014, at 9:47 pm, sebb <se...@gmail.com> wrote:
> On 30 June 2014 02:57, Brett Porter <br...@apache.org> wrote:
>> From 2014-06-29 17:46:36 to 17:48:00 UTC, all the builds had this error:
>>
>> svn: OPTIONS of 'http://svn.apache.org/repos/asf/commons/proper/codec/trunk': could not connect to server (http://svn.apache.org)
>>
>> Looks like the connection was ok when the next hourly schedule rolled around.
>>
>> I don't see any error for Directory, so maybe that particular one hung trying to connect giving you what you saw.
>
> Is there any way to add a timeout to the connection?
>
Usually it does, as the above commons errors showed. Not exactly sure what happened in the Directory case - looking again, it seems like it did complete the checkout in 2h45m (it uses externals, so it might have choked on one but then continued with the rest). Unfortunately there wasn't enough logging to figure out what happened, and it had already got past it by the time I had a look.
- Brett