Hi Milosz,

Thanks for this. We ultimately fixed this by adding "lava-signal: kmsg" to each of the test blocks.

Dave

On 06/07/2023 11:46, Milosz Wasilewski wrote:

Dave,

On Thu, Jul 6, 2023 at 11:13 AM Dave Pigott dave.pigott@collabora.com wrote:

...

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

I think you have a serial corruption here: https://lava.collabora.dev/scheduler/job/10987740#L2792

• export TESTRUN_ID=0_cros-local
• cd /lava-10987740/0/tests/0_cros-local
• cat uuid
• UUID=10987740_1.5.2.3.1
• set +x

Received signal: <STARTRUN> 0_cro<6

...

contrast, the following job, which is based on the same template, succeeds https://lava.collabora.dev/scheduler/job/11017230.

no corruption here:

• export TESTRUN_ID=0_cros-local
• cd /lava-11017230/0/tests/0_cros-local
• cat uuid
• UUID=11017230_1.6.2.3.1
• set +x

<LAVA_SIGNAL_STARTRUN 0_cros-local 11017230_1.6.2.3.1>

Hope this observation helps :)

Best Regards, Milosz

...

Is this genuinely a LAVA bug or do we have a job definition problem?

Thanks

Dave

-- Dave Pigott Principal Engineer

Collabora Ltd. Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK Registered in England & Wales, no. 5513718

---

Lava-devel mailing list -- lava-devel@lists.lavasoftware.org To unsubscribe send an email to lava-devel-leave@lists.lavasoftware.org