From: Rohitashv Kumar <rohit.kuma1313@gmail.com>
To: qemu-devel@nongnu.org
Cc: Fabiano Rosas <farosas@suse.de>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Rohitashv Kumar <roohiit@amazon.de>
Subject: [PATCH 3/3] tests/qtest/pxe-test: skip per-row cases whose machine is unavailable
Date: Fri, 17 Jul 2026 08:18:36 +0000 [thread overview]
Message-ID: <20260717081845.2439849-4-rohit.kuma1313@gmail.com> (raw)
In-Reply-To: <20260717081845.2439849-1-rohit.kuma1313@gmail.com>
From: Rohitashv Kumar <roohiit@amazon.de>
The x86 test table mixes 'pc' and 'q35' rows. When QEMU is built without
the i440fx/pc machine, the 'pc' rows fail with "unsupported machine type".
Add a per-row qtest_has_machine() check in test_batch(), mirroring the
existing per-row qtest_has_device() guard, so rows for an unavailable
machine are skipped while the others (e.g. q35) still run.
Signed-off-by: Rohitashv Kumar <roohiit@amazon.de>
---
tests/qtest/pxe-test.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tests/qtest/pxe-test.c b/tests/qtest/pxe-test.c
index a3f900fb..e85dec5a 100644
--- a/tests/qtest/pxe-test.c
+++ b/tests/qtest/pxe-test.c
@@ -108,6 +108,10 @@ static void test_batch(const testdef_t *tests, bool ipv6)
const testdef_t *test = &tests[i];
char *testname;
+ if (!qtest_has_machine(test->machine)) {
+ continue;
+ }
+
if (!qtest_has_device(test->model)) {
continue;
}
--
2.47.3
next prev parent reply other threads:[~2026-07-17 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 8:18 [PATCH 0/3] tests/qtest: make PCI tests resilient to a compiled-out i440fx/pc machine Rohitashv Kumar
2026-07-17 8:18 ` [PATCH 1/3] tests/qtest/device-plug-test: skip pc tests when 'pc' machine is unavailable Rohitashv Kumar
2026-07-17 8:18 ` [PATCH 2/3] tests/qtest/drive_del-test: " Rohitashv Kumar
2026-07-17 8:18 ` Rohitashv Kumar [this message]
2026-08-19 13:12 ` [PATCH 0/3] tests/qtest: make PCI tests resilient to a compiled-out i440fx/pc machine Fabiano Rosas
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=20260717081845.2439849-4-rohit.kuma1313@gmail.com \
--to=rohit.kuma1313@gmail.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roohiit@amazon.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.