test: Separate out the exception handling
The tests currently catch a very broad Exception in each case. This is thrown even in the event of a coding error. We want to handle exceptions differently depending on their severity, so that we can avoid hour-long delays waiting for a board that is clearly broken. As a first step, create some new exception types, separating out those which are simply an unexpected result from executed a command, from those which indicate some kind of hardware failure. Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
@@ -16,6 +16,17 @@ import traceback
|
||||
class Timeout(Exception):
|
||||
"""An exception sub-class that indicates that a timeout occurred."""
|
||||
|
||||
class BootFail(Exception):
|
||||
"""An exception sub-class that indicates that a boot failure occurred.
|
||||
|
||||
This is used when a bad pattern is seen when waiting for the boot prompt.
|
||||
It is regarded as fatal, to avoid trying to boot the again and again to no
|
||||
avail.
|
||||
"""
|
||||
|
||||
class Unexpected(Exception):
|
||||
"""An exception sub-class that indicates that unexpected test was seen."""
|
||||
|
||||
class Spawn:
|
||||
"""Represents the stdio of a freshly created sub-process. Commands may be
|
||||
sent to the process, and responses waited for.
|
||||
|
Reference in New Issue
Block a user