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
I've registered another blueprint. This time on LAVA Dispatcher. The
goal is similar as the previous blueprint about device manager, to
gather feedback and to propose some small steps sub-blueprints that
could be scheduled in 2012.04.
The general goal is to improve the way we run tests by making them more
reliable and more featureful (richer in state) at the same time.
Please read and comment on the mailing list
https://blueprints.launchpad.net/lava-dispatcher/+spec/lava-dispatcher-de-e…
Thanks
ZK
--
Zygmunt Krynicki
Linaro Validation Team