Hi Stefan,

Thank you for showing me that post. It has more or less confirmed an idea I had as to why it may not be working. I had suspected it may be lava matching to the previous prompt instead of the current, which at the time seemed both plausible and yet ridiculous, but it is the best explanation for overlapping commands. The particular delay I found most effective until now wasn't as crazy as 100ms, but several delays for commands at approximately 5ms each.

There is not much I can do to change the test or device configuration for the prompt, as my device simply uses '#' as the prompt for commands. There is something I have noticed though, that seems unique to telnet, which is that there is some kind of an "echo", where there is an empty prompt after every command execution. minicom does not have this, nor does ssh. Iirc, this can be disabled in interactive tests. Is there a way to disable this for regular tests or in general? I am not sure it will be effective at solving the issue, but it is worth a shot.

If you want to see logs, I will paste the part of the plain log here where the failure happens:
[...]

After that I cancelled the test as I didn't want or need to wait for it to time out, since intervention would be required to get the test to finish, and I am just trying to get it working. As of this reply that is the latest test I have run.
If there is anything else needed to help diagnose the issue and come up with a solution, please let me know so I can do my best to provide more information.

Best regards,
Michael
_______________________________________________
lava-users mailing list -- lava-users@lists.lavasoftware.org
To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s