tree 987ef025a44ad100c713d5da3e45c13e19ef9964
parent 636f38d83a7e0e6ca076ae65e086c800337fb3a3
author Stephen Warren <swarren@nvidia.com> 1453491009 -0700
committer Simon Glass <sjg@chromium.org> 1454040083 -0700

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>