On 20 January 2016 at 15:15, Stephen Warren <swar...@wwwdotorg.org> wrote: > From: Stephen Warren <swar...@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 <swar...@nvidia.com> > --- > test/py/conftest.py | 1 + > test/py/u_boot_console_base.py | 38 ++++++++++++++++++++++++++++++++++++++ > 2 files changed, 39 insertions(+)
Acked-by: Simon Glass <s...@chromium.org> _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
