FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: fstests@vger.kernel.org
Subject: Re: [PATCH RFC] check: add new option "--loop <n>" which runs each test multiple times
Date: Tue, 5 May 2026 15:34:09 +0200	[thread overview]
Message-ID: <20260505133409.GA49070@macsyma.local> (raw)
In-Reply-To: <20260415213248.1795275-1-tytso@mit.edu>

On Wed, Apr 15, 2026 at 05:32:48PM -0400, Theodore Ts'o wrote:
> Teach the check script a new option --loop, which re-run each test
> multiple times.  This works very similarly to to -L, which will retry
> a particular test after it first fails, except that the test is rerun
> unconditionally.

Ping?  Does anyone have a preference between adding a new option,
--loop, or changing the heaviour of the -i option?

> This differs from the "-i <n>" option, which iterates each set of
> tests <n> times instead of each test.  The -i option is problematic in
> two ways.  First, it doesn't save the test artifacts from each test run.
> This is unfortunate because when the developer is trying to debug a
> flaky test failure, running "check -i 100" will run a test 100 times,
> but if only the 42nd test fails, the NNN.out.bad file for that failing
> test run is not preserved.  The second difference between --loop and
> -i is the result.xml file is rewritten after each test set, so we do
> not have the cumulative statistics of the 100 test runs in the junit
> XML file.

						- Ted

  reply	other threads:[~2026-05-05 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 21:32 [PATCH RFC] check: add new option "--loop <n>" which runs each test multiple times Theodore Ts'o
2026-05-05 13:34 ` Theodore Tso [this message]
2026-05-07 20:20   ` Zorro Lang
2026-05-07 19:50 ` 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=20260505133409.GA49070@macsyma.local \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    /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