summaryrefslogtreecommitdiff
path: root/board/BuS
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2016-01-22 19:30:09 (GMT)
committerSimon Glass <sjg@chromium.org>2016-01-29 04:01:23 (GMT)
commitc10eb9d39fb54f435dbd632f71c760e4a887a015 (patch)
tree987ef025a44ad100c713d5da3e45c13e19ef9964 /board/BuS
parent636f38d83a7e0e6ca076ae65e086c800337fb3a3 (diff)
downloadu-boot-c10eb9d39fb54f435dbd632f71c760e4a887a015.tar.xz
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>
Diffstat (limited to 'board/BuS')
0 files changed, 0 insertions, 0 deletions