diff mbox series

[PULL,13/13] device-crash-test: Ignore errors about a bus not being available

Message ID 20210401131220.3252320-14-thuth@redhat.com
State New
Headers show
Series [PULL,01/13] MAINTAINERS: Fix tests/migration maintainers | expand

Commit Message

Thomas Huth April 1, 2021, 1:12 p.m. UTC 
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>
---
 scripts/device-crash-test | 1 +
 1 file changed, 1 insertion(+)
diff mbox series

Patch

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},