From: Thomas Huth <thuth@redhat.com>
To: kvm@vger.kernel.org, "Nico Böhr" <nrb@linux.ibm.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>
Cc: Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>
Subject: [kvm-unit-tests PATCH v2] scripts/arch-run.bash: Drop the dependency on "jq"
Date: Thu, 31 Jul 2025 13:05:01 +0200 [thread overview]
Message-ID: <20250731110501.38034-1-thuth@redhat.com> (raw)
From: Thomas Huth <thuth@redhat.com>
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.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
v2: Use [[:blank:]]* as suggested by Claudio
scripts/arch-run.bash | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/scripts/arch-run.bash b/scripts/arch-run.bash
index 58e4f93f..4642cf95 100644
--- a/scripts/arch-run.bash
+++ b/scripts/arch-run.bash
@@ -287,11 +287,6 @@ do_migration ()
run_panic ()
{
- if ! command -v jq >/dev/null 2>&1; then
- echo "${FUNCNAME[0]} needs jq" >&2
- return 77
- fi
-
trap 'trap - TERM ; kill 0 ; exit 2' INT TERM
trap 'rm -f ${qmp}.in ${qmp}.out' RETURN EXIT
@@ -303,8 +298,7 @@ run_panic ()
-mon chardev=mon,mode=control -S &
echo '{ "execute": "qmp_capabilities" }{ "execute": "cont" }' > ${qmp}.in
- 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
echo "FAIL: guest did not panic"
ret=3
else
--
2.50.1
reply other threads:[~2025-07-31 11:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250731110501.38034-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).