baseline failures on trogdor

[r-c-n]

https://linux.kernelci.org/test/job/chrome-platform/branch/for-kernelci/kernel/v6.1-rc1-12-g52f572342440/plan/baseline/

This is a recurrent issue in Collabora LAVA lab on trogdor Chromebooks, some tests fail randomly due to the interleaving of kernel output in the console. The racy console outputs cause LAVA to fail to parse certain strings.

[penvirus]

I was looking a baseline.login test failure.

• A PASS case.
• A FAIL case.

I suspect if it is an issue for parsing the prompt because I found the following error messages in the FAIL case:

03:01:54.290909  Unknown test uuid. The STARTRUN signal for this test action was not received correctly.
03:01:54.291074  end: 3.1 lava-test-shell (duration 00:00:00) [common]
03:01:54.291256  lava-test-retry failed: 1 of 1 attempts. 'Invalid TESTCASE signal'

[r-c-n]

Actually, the problem is that LAVA misses something in the serial output and doesn't get a STARTRUN signal. This is a known issue of the trogdor Chromebooks in the Collabora LAVA lab at least, it affects most of the test runs and there's an ongoing effort to fix this or to find a workaround.

This is an example of the same type of job running fine: https://lava.collabora.dev/scheduler/job/8303390

[nfraprado]

Being investigated in #380.