These errors are expected, so they shouldn't clog up terminal output. In
the event that they're *not* expected, we'll be seeing an awful lot more
output concerning the nature of the failure.
Reported-by: Thomas Huth <th...@redhat.com>
Signed-off-by: John Snow <js...@redhat.com>
Tested-by: Thomas Huth <th...@redhat.com>
Message-id: 20211111143719.2162525-5-js...@redhat.com
Signed-off-by: John Snow <js...@redhat.com>
---
scripts/device-crash-test | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index d91e8616ef..49bcd61b4f 100755
--- a/scripts/device-crash-test
+++ b/scripts/device-crash-test
@@ -499,6 +499,12 @@ def main():
lvl = logging.WARN
logging.basicConfig(stream=sys.stdout, level=lvl, format='%(levelname)s:
%(message)s')
+ if not args.debug:
+ # Async QMP, when in use, is chatty about connection failures.
+ # This script knowingly generates a ton of connection errors.
+ # Silence this logger.
+ logging.getLogger('qemu.aqmp.qmp_client').setLevel(logging.CRITICAL)
+
fatal_failures = []
wl_stats = {}
skipped = 0
--
2.31.1
