aboutsummaryrefslogtreecommitdiff
path: root/scripts/device-crash-test
diff options
context:
space:
mode:
authorThomas Huth <thuth@redhat.com>2021-03-23 17:47:18 +0100
committerThomas Huth <thuth@redhat.com>2021-04-01 14:28:39 +0200
commitca89d15f8e42f2e5eac5bd200af38fdbfb32e875 (patch)
tree4e140ae0de2ff34e0efd97287dd27122ab0082df /scripts/device-crash-test
parent69c5d14dc87cc41819cbba01c7eab71d9be2b052 (diff)
device-crash-test: Ignore errors about a bus not being available
Recent QEMU versions now sometimes exit cleanly with an error message that a bus is not available for a specified device. Don't flag those as an error in the device-crash-test script. Message-Id: <20210323164718.1393792-1-thuth@redhat.com> Acked-by: John Snow <jsnow@redhat.com> Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'scripts/device-crash-test')
-rwxr-xr-xscripts/device-crash-test1
1 files changed, 1 insertions, 0 deletions
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 6d809ac711..8331c057b8 100755
--- a/scripts/device-crash-test
+++ b/scripts/device-crash-test
@@ -175,6 +175,7 @@ ERROR_RULE_LIST = [
{'log':r"Multiple VT220 operator consoles are not supported"},
{'log':r"core 0 already populated"},
{'log':r"could not find stage1 bootloader"},
+ {'log':r"No '.*' bus found for device"},
# other exitcode=1 failures not listed above will just generate INFO messages:
{'exitcode':1, 'loglevel':logging.INFO},