All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: [RFC PATCH 1/4] check: add long aliases --iterate and --iterate-while-successful
Date: Wed, 11 Nov 2026 01:09:17 +0800	[thread overview]
Message-ID: <20261110170920.3302511-2-zlang@kernel.org> (raw)
In-Reply-To: <20261110170920.3302511-1-zlang@kernel.org>

The -i and -I options iterate the whole test list, but their
single-letter names don't describe what they do.  Add the long aliases
--iterate and --iterate-while-successful so that they can be named
consistently with the --loop family of per-test looping options that
will be added next.

Signed-off-by: Zorro Lang <zlang@kernel.org>
---
 check | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/check b/check
index afe855bc..538f22cf 100755
--- a/check
+++ b/check
@@ -62,8 +62,9 @@ General options:
     -b                      brief test summary
     -d                      dump test output to stdout
     -h, --help              show this help message
-    -i <n>                  iterate the test list <n> times
-    -I <n>                  iterate the test list <n> times, but stops
+    -i, --iterate <n>       iterate the test list <n> times
+    -I, --iterate-while-successful <n>
+                              iterate the test list <n> times, but stops
                               iterating further in case of any test failure
     -l                      line mode diff
     -L <n>                  loop tests <n> times following a failure, measuring
@@ -388,7 +389,7 @@ process_remain_tests()
 parse_check_args()
 {
 	local short_opts="g:x:X:e:E:s:S:lnri:I:TdbR:L:h"
-	local long_opts="fs:,exact-order,large-fs,extra-space:,udiff,help"
+	local long_opts="fs:,exact-order,large-fs,extra-space:,udiff,help,iterate:,iterate-while-successful:"
 
 	compat_old_option "$@"
 
@@ -466,11 +467,11 @@ parse_check_args()
 			fi
 			exact_order=true
 			;;
-		-i)
+		-i|--iterate)
 			iterations=$2
 			shift
 			;;
-		-I)
+		-I|--iterate-while-successful)
 			iterations=$2
 			istop=true
 			shift
-- 
2.56.0


  reply	other threads:[~2026-11-10 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 17:09 [RFC PATCH 0/4] check: add --loop* family options for repeating tests Zorro Lang
2026-11-10 17:09 ` Zorro Lang [this message]
2026-11-10 17:09 ` [RFC PATCH 2/4] check: add --loop option to run each test multiple times Zorro Lang
2026-11-10 17:09 ` [RFC PATCH 3/4] check: add --loop-on-fail long name for -L Zorro Lang
2026-11-10 17:09 ` [RFC PATCH 4/4] check: add --loop-while-successful option Zorro Lang

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=20261110170920.3302511-2-zlang@kernel.org \
    --to=zlang@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.