[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-validation
Subject:    [Linaro-validation] deploy timeouts
From:       dave.pigott () linaro ! org (Dave Pigott)
Date:       2012-03-28 13:55:47
Message-ID: 7D458F63-5C82-4442-B502-5641E9FCA642 () linaro ! org
[Download RAW message or body]

On 28 Mar 2012, at 14:21, Fathi Boudra wrote:

> On 20 March 2012 16:22, Dave Pigott wrote:
>> Hi,
>> 
>> I think we need to seriously look at allowing a timeout parameter around
>> "deploy_linaro_image", because vexpress is going to need around 4 hours to
>> deploy a full desktop, and it seems crazy that we should hard code that big
>> a timeout into master.py for *all* platforms.
>> 
>> I realise there is an issue as to which part the timeout is applied to and
>> how it's apportioned, but even if we just allowed to pass through the whole
>> timeout to each stage it would be better than what we have at the moment.
>> 
>> Thoughts?
> 
> Follow up to Dave initial thread, we didn't have reached a conclusion.
> He reported https://bugs.launchpad.net/lava-dispatcher/+bug/961926
> Could we plan (and assign someone) to land a fix for this bug?
> 
> Cheers,
> 
> Fathi

Hi Fathi,

There's also this MP: https://code.launchpad.net/~dpigott/lava-dispatcher/increase-timeout/+merge/98630

Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linaro.org/pipermail/linaro-validation/attachments/20120328/ab762056/attachment.html>

[prev in list] [next in list] [prev in thread] [next in thread]