test/py: check for bad patterns everywhere we wait
authorStephen Warren <swarren@nvidia.com>
Thu, 28 Jan 2016 06:57:49 +0000 (23:57 -0700)
committerSimon Glass <sjg@chromium.org>
Fri, 29 Jan 2016 04:01:24 +0000 (21:01 -0700)
commit0c6189b5d60a2b0fcec65f3513bad7eee289da3f
tree85362f09000df53430d79f9ce88b131e9ac32be0
parente4119ebb6dabf9bc84914b648f81c2f1b8fe76e1
test/py: check for bad patterns everywhere we wait

Currently, bad patterns are only honored when executing a shell command.
Other cases, such as the initial boot-up of U-Boot or when interacting
with command output rather than gathering all output prior to the shell
prompt, do not currently look for bad patterns in console output. This
patch makes sure that bad patterns are honored everywhere.

One benefit of this change is that if U-Boot sandbox fails to start up,
the error message it emits can be caught immediately, rather than relying
on a (long) timeout when waiting for the expected signon message and/or
command prompt.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Simon Glass <sjg@chromium.org>
test/py/u_boot_console_base.py