Hi Milosz and Kevin,

let me explain the issue a bit:

we want to use
failure_retry: 2
in the deploy section.

But for that we need the overall deployimages timeout to be let's say 25 minutes and the http_download timeout to be e.g. 10 minutes.
Currently everything is 25 minutes.

So do I understand this right, that
- deploy:
timeout:
minutes: 25
Overrides all timeout below 'deploy' to 25 minutes ?

So would we have to remove that in favour of  a more detailed setting of the top-level:
timeouts:
job:
minutes: 80
action:
minutes: 15
connection:
minutes: 5
connections:
lava-test-shell:
minutes: 10

????



On Tue, Apr 30, 2019 at 10:02 AM Milosz Wasilewski <milosz.wasilewski@linaro.org> wrote:
On Mon, 29 Apr 2019 at 22:54, Kevin Hilman <khilman@baylibre.com> wrote:
>
> Hello,
>
> I'm trying to customize the http-download timeout as documented[1], but
> I doesn't seem to work.  The global deploy time always seems to win.
>
> Based on the doc, I did this, I added the following to my job[2]
>
> timeouts:
>   actions:
>     http-download:
>       minutes: 15
>
> However, in the job output, you can see that the http-download timeout
> value is set to 25 min (1500 sec) which is coming from the deploy action
> timeout.
>
> I got the same result when tryin to use timeouts: connections:
>
> What am I missing?

I'm not 100% sure but the timeouts defined in the 'timeouts' section
are considered 'default' and are always overwritten by timeouts
defined in actions themselves.

milosz

>
> Kevin
>
> [1] https://validation.linaro.org/static/docs/v2/timeouts.html?highlight=http_download#inheriting-timeouts-from-the-device-configuration
> [2] https://lava.automotivelinux.org/scheduler/job/3270/definition#defline44
> [3] https://lava.automotivelinux.org/scheduler/job/3270#action_1-1-1
>
> _______________________________________________
> Lava-users mailing list
> Lava-users@lists.lavasoftware.org
> https://lists.lavasoftware.org/mailman/listinfo/lava-users