diff options
| author | Stephen Warren <swarren@nvidia.com> | 2016-01-25 15:07:58 -0700 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2016-01-28 21:01:23 -0700 |
| commit | e787a58fe2544497bbc75066e0bc62868c7c4e65 (patch) | |
| tree | 3bd03580986b103c5665b93b9df4ee77970430be /arch | |
| parent | c6db965f67c01c9ac6570eed690103f3ea30b3c4 (diff) | |
| download | u-boot-imx-e787a58fe2544497bbc75066e0bc62868c7c4e65.zip u-boot-imx-e787a58fe2544497bbc75066e0bc62868c7c4e65.tar.gz u-boot-imx-e787a58fe2544497bbc75066e0bc62868c7c4e65.tar.bz2 | |
test/py: make crash detection more robust
test/py contains logic to detect the target crashing and rebooting by
searching the console output for a U-Boot signon message, which will
presumably be emitted when the system boots after the crash/reset.
Currently, this logic only searches for the exact signon message that
was printed by the U-Boot version under test, upon the assumption that
binary is written into flash, and hence will be the version booted after
any reset. However, this is not a valid assumption; some test setups
download the U-Boot-under-test into RAM and boot it from there, and in
such a scenario an arbitrary U-Boot version may be located in flash and
hence run after any reset.
Fix the reset detection logic to match any U-Boot signon message. This
prevents false negatives.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions