test/py: drain console log at the end of any failed test
authorStephen Warren <swarren@nvidia.com>
Fri, 22 Jan 2016 19:30:09 +0000 (12:30 -0700)
committerSimon Glass <sjg@chromium.org>
Fri, 29 Jan 2016 04:01:23 +0000 (21:01 -0700)
commitc10eb9d39fb54f435dbd632f71c760e4a887a015
tree987ef025a44ad100c713d5da3e45c13e19ef9964
parent636f38d83a7e0e6ca076ae65e086c800337fb3a3
test/py: drain console log at the end of any failed test

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@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
test/py/conftest.py
test/py/u_boot_console_base.py