Hi Milosz,

Per the discussion here https://gitlab.com/lava/lava/-/merge_requests/2800#note_2503048170, what about we set the default download retries back to 1? When the retries is increased explicitly, the timeout should be set to 'retries * timeout'. Make sense?

Cheers,

Chase

On Fri, 9 May 2025 at 18:11, Milosz Wasilewski <milosz.wasilewski@foundries.io> wrote:

Hi,

After the 2025.02 release download timeouts are terribly broken. This
should have never happened. LAVA is silently dividing the action
timeout by number of repetitions:
https://gitlab.com/lava/lava/-/wikis/releases/2025.02#timeout-and-retries
https://gitlab.com/lava/lava/-/commit/07b13b5e4a2bb335dcfff155974ade81ef17b002#11117d66127e662ae023f0e091184616da8585e7_148_146

This causes perfectly good jobs to fail. Example:
https://lava.infra.foundries.io/scheduler/job/73929

If such change is required it should have been done with explicit
parameter set in the job definition. In the current form I consider it
a bug. The only way to work around this bug is to set the timeout to
some ridiculous number (3 times as long as it is normally required).
IMHO this should be reverted before the next release.

Best Regards,
Milosz
_______________________________________________
lava-users mailing list -- lava-users@lists.lavasoftware.org
To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s