[U-Boot] [PATCH V2 3/8] test/py: drain console log at the end of any failed test
Simon Glass
sjg at chromium.org
Fri Jan 22 21:14:32 CET 2016
On 22 January 2016 at 12:30, Stephen Warren <swarren at wwwdotorg.org> wrote:
> From: Stephen Warren <swarren at nvidia.com>
>
> Tests may fail for a number of reasons, and in particular for reasons
> other than a timeout waiting for U-Boot to print expected data. If the
> last operation that a failed test performs is not waiting for U-Boot to
> print something, then any trailing output from U-Boot during that test's
> operation will not be logged as part of that test, but rather either
> along with the next test, or even thrown away, potentiall hiding clues
> re: the test failure reason.
>
> Solve this by explicitly draining (and hence logging) the U-Boot output
> in the case of failed tests.
>
> Signed-off-by: Stephen Warren <swarren at nvidia.com>
> Acked-by: Simon Glass <sjg at chromium.org>
> ---
> test/py/conftest.py | 1 +
> test/py/u_boot_console_base.py | 38 ++++++++++++++++++++++++++++++++++++++
> 2 files changed, 39 insertions(+)
Applied to u-boot-dm, thanks!
More information about the U-Boot
mailing list