[Buildroot] Issue with capture of emulator output in runtime test infra

Peter Korsgaard peter at korsgaard.com
Mon Oct 4 11:52:06 UTC 2021


>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at bootlin.com> writes:

 > Hello,
 > I've been working on some additional test cases in support/testing/,
 > and stumbled across an issue in the infrastructure, which I thought I
 > should report before forgetting about it.

..

 > While we would have expected output[] to contain just a single element,
 > "200", which is really the only output of the command. For now, I've
 > worked around this by looking at output[-1] in my test case, which is
 > good enough because I only care about one line of output.

 > However, I'm not really sure how to fix this in the Emulator.run() core
 > itself. Perhaps we should not be using the -serial stdio (which
 > requires interacting on stdin/stdout), but instead use a separate
 > telnet port (but then there's always the issue of which port to use) ?

Just a hack, but how about we add a marker after each shell command (#
MARKER) and just strip everything util after the marker?

-- 
Bye, Peter Korsgaard


More information about the buildroot mailing list