With delivery of May, we can now defined timer for each test of a job.
Some of our tests are not correctly executed and then timeout expired.
Timeouts are fatal - if any part of a LAVA test job times out, that is an error, so the job will be incomplete.
Failure-retry exists to attempt the same operation again but if there are "allowable" timeouts, that must be handled by the test writer using a custom script that knows exactly how long to wait before giving up, clean up after the broken operation and then exit zero so that the next stage can occur. The test definition then calls that script instead of the original command.
Think about how this would be done if you were running the same test on a local system and create a script which can handle the failing test. In that script, when the failure is detected, if lava-test-case exists in $PATH, use that to report --result fail before exiting zero. If lava-test-case is not in $PATH, use echo or print etc to describe what has happened.