aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Huth <thuth@redhat.com>2021-11-12 08:22:20 +0100
committerThomas Huth <thuth@redhat.com>2021-11-17 10:20:17 +0100
commit418ce0201ff6f4c9d9560eaea15ff393c2cd7412 (patch)
treea1b6c0c23dc4d7145718956f156682683cef0aa9
parent9f73de8df0335c9387f4ee39e207a65a1615676f (diff)
Revert "device-crash-test: Ignore errors about a bus not being available"
This reverts commit ca89d15f8e42f2e5eac5bd200af38fdbfb32e875. There is already an entry for this kind of messages earlier in the ERROR_RULE_LIST - when I added this patch, I just got fooled by the other errors that occur due to a race between QMP connection and QEMU terminating early (which still spit out the 'No bus found' messages in their backtrace), but these other problems have now fortunately been tackled by John Snow, so we certainly don't need this duplicated entry here anymore. Message-Id: <20211112072220.108580-1-thuth@redhat.com> Signed-off-by: Thomas Huth <thuth@redhat.com>
-rwxr-xr-xscripts/device-crash-test1
1 files changed, 0 insertions, 1 deletions
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index 3db0ffe5b8..1c73dac93e 100755
--- a/scripts/device-crash-test
+++ b/scripts/device-crash-test
@@ -176,7 +176,6 @@ 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},