On 8 September 2017 at 14:56, Denis HUMEAU denis.humeau@st.com wrote:

Hello,

My question looks pretty silly, but as Lava has a big set of features that I haven’t discovered yet, I dare ask.

Lava is designed for automatic testing. But everything cannot be fully automated, at least in a reasonable development time frame. More precisely, tests execution can be automated, but the test result needs to be given by a tester. This will happen for example in display or graphics tests.

There is work to automate display and graphics tests using HDMI dongles.

So, is there a simple way in Lava to let a tester give a manual test result, during or after the test execution? I already have in mind pretty complicated solutions based on Multinode, but simple is key here

Using a hacking session it is possible to send the same string to the console as LAVA is waiting to match as a pattern for a result. This generally does not work with calls to the MultiNode API as the signal handling there is different. Note that this behaviour is generally problematic and should not be relied upon for future support. The ability of (in particular) the kernel to emit messages to the console which interfere with this matching causes a variety of other bugs.