mirror of
https://github.com/brain-hackers/u-boot-brain
synced 2024-10-02 17:40:41 +09:00
c10eb9d39f
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> |
||
|---|---|---|
| .. | ||
| dfu | ||
| dm | ||
| env | ||
| fs | ||
| image | ||
| py | ||
| stdint | ||
| trace | ||
| ums | ||
| vboot | ||
| cmd_ut.c | ||
| command_ut.c | ||
| common.sh | ||
| compression.c | ||
| Kconfig | ||
| Makefile | ||
| time_ut.c | ||
| ut.c | ||