From: "Nico Boehr" <nrb@linux.ibm.com>
To: "Thomas Huth" <thuth@redhat.com>, <kvm@vger.kernel.org>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>
Cc: "Andrew Jones" <andrew.jones@linux.dev>,
"Janosch Frank" <frankja@linux.ibm.com>
Subject: Re: [kvm-unit-tests PATCH v2] scripts/arch-run.bash: Drop the dependency on "jq"
Date: Wed, 10 Sep 2025 09:57:17 +0200 [thread overview]
Message-ID: <DCOYKSEY6V79.3HE423J6WWXTT@linux.ibm.com> (raw)
In-Reply-To: <20250909045855.71512-1-thuth@redhat.com>
On Tue Sep 9, 2025 at 6:58 AM CEST, Thomas Huth wrote:
> For checking whether a panic event occurred, a simple "grep"
> for the related text in the output is enough - it's very unlikely
> that the output of QEMU will change. This way we can drop the
> dependency on the program "jq" which might not be installed on
> some systems.
Trying to understand which problem you're trying to solve here.
Is there any major distribution which doesn't have jq in its repos? Or any
reason why you wouldn't install it?
> diff --git a/scripts/arch-run.bash b/scripts/arch-run.bash
> index 36222355..16417a1e 100644
> --- a/scripts/arch-run.bash
> +++ b/scripts/arch-run.bash
> @@ -296,11 +296,6 @@ do_migration ()
>
> run_panic ()
> {
[...]
> - panic_event_count=$(jq -c 'select(.event == "GUEST_PANICKED")' < ${qmp}.out | wc -l)
> - if [ "$panic_event_count" -lt 1 ]; then
> + if ! grep -E -q '"event"[[:blank:]]*:[[:blank:]]*"GUEST_PANICKED"' ${qmp}.out ; then
This changes behaviour.
Now "event" can be arbitrarily deep nested in the JSON. It could even be
completely invalid JSON.
Not saying we shouldn't do this, it just comes with a cost and we need to see if
it's worth paying that.
next prev parent reply other threads:[~2025-09-10 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 4:58 [kvm-unit-tests PATCH v2] scripts/arch-run.bash: Drop the dependency on "jq" Thomas Huth
2025-09-09 13:49 ` Claudio Imbrenda
2025-09-09 16:05 ` Andrew Jones
2025-09-10 7:57 ` Nico Boehr [this message]
2025-09-10 9:00 ` Claudio Imbrenda
2025-09-10 9:06 ` Thomas Huth
2025-09-10 11:36 ` Nico Boehr
-- strict thread matches above, loose matches on Subject: below --
2025-07-31 11:05 Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DCOYKSEY6V79.3HE423J6WWXTT@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=andrew.jones@linux.dev \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox