* [PATCH] device-crash-test: Ignore errors about a bus not being available
@ 2021-03-23 16:47 Thomas Huth
2021-03-24 20:47 ` John Snow
0 siblings, 1 reply; 2+ messages in thread
From: Thomas Huth @ 2021-03-23 16:47 UTC (permalink / raw)
To: Eduardo Habkost, qemu-devel; +Cc: John Snow, Cleber Rosa
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.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
scripts/device-crash-test | 1 +
1 file changed, 1 insertion(+)
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},
--
2.27.0
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH] device-crash-test: Ignore errors about a bus not being available
2021-03-23 16:47 [PATCH] device-crash-test: Ignore errors about a bus not being available Thomas Huth
@ 2021-03-24 20:47 ` John Snow
0 siblings, 0 replies; 2+ messages in thread
From: John Snow @ 2021-03-24 20:47 UTC (permalink / raw)
To: Thomas Huth, Eduardo Habkost, qemu-devel; +Cc: Cleber Rosa
On 3/23/21 12:47 PM, Thomas Huth wrote:
> 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.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> scripts/device-crash-test | 1 +
> 1 file changed, 1 insertion(+)
>
> 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},
>
ACK, though I don't consider myself a maintainer of this file. Whose
tree does it go in? (Trivial, if nobody's?)
--js
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-03-24 20:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-23 16:47 [PATCH] device-crash-test: Ignore errors about a bus not being available Thomas Huth
2021-03-24 20:47 ` John Snow
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).