From: Nicholas Piggin <npiggin@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Andrew Jones <andrew.jones@linux.dev>,
kvm@vger.kernel.org
Subject: [kvm-unit-tests PATCH v2 1/2] doc: update unittests doc
Date: Wed, 5 Jun 2024 18:09:40 +1000 [thread overview]
Message-ID: <20240605080942.7675-2-npiggin@gmail.com> (raw)
In-Reply-To: <20240605080942.7675-1-npiggin@gmail.com>
Document the special groups, check path restrictions, and a small fix
for check option syntax.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
docs/unittests.txt | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/docs/unittests.txt b/docs/unittests.txt
index 6ff9872cf..c4269f623 100644
--- a/docs/unittests.txt
+++ b/docs/unittests.txt
@@ -69,8 +69,11 @@ groups
groups = <group_name1> <group_name2> ...
Used to group the test cases for the `run_tests.sh -g ...` run group
-option. Adding a test to the nodefault group will cause it to not be
-run by default.
+option. The group name is arbitrary, except for these special groups:
+- Tests in the "nodefault" group are not run by default (with no -g option).
+- Tests in the "migration" group are run with the migration harness and
+ are expected to make migrate_*() calls.
+- Tests in the "panic" group expect QEMU to enter the GUEST_PANICKED state.
accel
-----
@@ -89,8 +92,10 @@ Optional timeout in seconds, after which the test will be killed and fail.
check
-----
-check = <path>=<<value>
+check = <path>=<value>
Check a file for a particular value before running a test. The check line
can contain multiple files to check separated by a space, but each check
parameter needs to be of the form <path>=<value>
+
+The path and value cannot contain space, =, or shell wildcard characters.
--
2.43.0
next prev parent reply other threads:[~2024-06-05 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 8:09 [kvm-unit-tests PATCH v2 0/2] misc docs/build/CI improvements Nicholas Piggin
2024-06-05 8:09 ` Nicholas Piggin [this message]
2024-06-05 10:46 ` [kvm-unit-tests PATCH v2 1/2] doc: update unittests doc Andrew Jones
2024-06-05 8:09 ` [kvm-unit-tests PATCH v2 2/2] gitlab-ci: Always save artifacts Nicholas Piggin
2024-06-05 10:51 ` [kvm-unit-tests PATCH v2 0/2] misc docs/build/CI improvements 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=20240605080942.7675-2-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=andrew.jones@linux.dev \
--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