Hello,
I have a LAVA job with long running test, so I put a timeout of 180 minutes in the test action itself[1].
However, but the job times out after 3989 seconds (~ 66 min)[2].
Looking closer at the "Timing" section of the job, I see that lava-test-shell indeed has a timeout of ~3989 seconds, but I have no idea where that number comes from. That's neither the 10 minutes in the default "timeouts" section, nor the 180 minutes I put in the "test" action.
Hmm, after almost pushing send on this, I now seeing that in the "timeouts" sections, the whole job has a timeout of 70 minutes. So, I assume that means an absolute max, even if one of the actions puts a higher timeout?
So I guess this email now turns into a feature request rather than a bug report.
Maybe LAVA should show a warning at the top of the job if any of the actions has a timeout that's longer than the job timeout.
Kevin
[1] http://lava.baylibre.com:10080/scheduler/job/60374/definition#defline89 [2] http://lava.baylibre.com:10080/scheduler/job/60374#results_694663