Interesting reboot performance... our builds have been waiting for 1.5 hrs.
EdB
On Fri, Dec 13, 2013 at 8:42 AM, OmPrakash Muppirala
wrote:
> On Thu, Dec 12, 2013 at 11:30 PM, Erik de Bruin wrote:
>
>> Hi Gavin,
>>
>> As 'windows2' has, as far as i can tell, not been configured to run
>> the
Guinness called. It's official, we now have the longest reboot time in
recorded history: > 24 hrs ;-)
EdB
On Fri, Dec 13, 2013 at 9:07 AM, Erik de Bruin wrote:
> Interesting reboot performance... our builds have been waiting for 1.5 hrs.
>
> EdB
>
>
>
> On Fri, Dec 13, 2013 at 8:42 AM, OmPraka
Gavin, please, please, pretty please, can you have a look at the
'windows1' situation? Please?
Or, if you don't have time - which I would totally understand and
respect - please tell us so one of the other 8 admins on the
'windows1' slave can step in.
Our project needs the builds, as I explained
Erik,
Let's try to continue to be patient. It is a weekend, and there is a
reasonable chance that whatever caused our build to break totally broke
the server on reboot.
-Alex
On 12/13/13 10:48 PM, "Erik de Bruin" wrote:
>Guinness called. It's official, we now have the longest reboot time in
>r
I'm sorry, but it's been 10 days now and in that time we've seen very
little activity from the 'powers that be'. We've even had to make
substantial changes to our own project to work around the failure of
the slave and now we've implemented that, the slave has been offline
for more than a day.
If
