Searched hist:c10eb9d39fb54f435dbd632f71c760e4a887a015 (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/test/py/ |
| H A D | conftest.py | c10eb9d39fb54f435dbd632f71c760e4a887a015 Fri Jan 22 19:30:09 UTC 2016 Stephen Warren <swarren@nvidia.com> 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>
|
| H A D | u_boot_console_base.py | c10eb9d39fb54f435dbd632f71c760e4a887a015 Fri Jan 22 19:30:09 UTC 2016 Stephen Warren <swarren@nvidia.com> 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>
|