On 02/27/2012 09:02 PM, Mustafa Faraj wrote:
Hi Andy and Zygmunt,
I am working with lava-dispatch and trying to write my own test commands. For my use case, I would like to get the full output of the tests that run on the DUT (Overo board), as opposed to only the lines matching the self.proc.pexpect(pattern). I dug a bit through the code and saw that the proc's logfile is defined as a SerialIO class, but I am not sure how to get the full output through that. How do you recommend that I go about that?
I'm CC-ing this to linaro-validation.
Normally after the test is done you can see both the per-test command and full serial log. Is that what you need?
Thanks ZK
I am trying to send custom tests (that do not use the lava-test framework) to the board and I want to get the full output of the the test (from the DUT's stdout/stderr). This is a part of the same project that Ash was asking you about on IRC, and from that discussion we figured it would be more suitable to use the lava-android-test framework to do what we need; however I am still curious to know if there's a way of doing this.
Thanks, -Mustafa
On Mon, Feb 27, 2012 at 1:19 PM, Zygmunt Krynicki < zygmunt.krynicki@canonical.com> wrote:
On 02/27/2012 09:02 PM, Mustafa Faraj wrote:
Hi Andy and Zygmunt,
I am working with lava-dispatch and trying to write my own test commands. For my use case, I would like to get the full output of the tests that run on the DUT (Overo board), as opposed to only the lines matching the self.proc.pexpect(pattern). I dug a bit through the code and saw that the proc's logfile is defined as a SerialIO class, but I am not sure how to get the full output through that. How do you recommend that I go about that?
I'm CC-ing this to linaro-validation.
Normally after the test is done you can see both the per-test command and full serial log. Is that what you need?
Thanks ZK
linaro-validation@lists.linaro.org