Hi all,
We've been noticing an increase in a particular error, reported as a lava bug by lava itself. An example job is https://lava.collabora.dev/scheduler/job/10987740 - however, for contrast, the following job, which is based on the same template, succeeds https://lava.collabora.dev/scheduler/job/11017230.
Is this genuinely a LAVA bug or do we have a job definition problem?
Thanks
Dave