public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
	ritesh.list@gmail.com, ojaswin@linux.ibm.com, djwong@kernel.org,
	zlang@kernel.org, david@fromorbit.com
Subject: Re: [PATCH v2 0/3] Add support for -q <n> unconditional loop
Date: Wed, 9 Apr 2025 22:04:14 +0530	[thread overview]
Message-ID: <5fe56381-72c4-41ed-a4b6-d13eff1e427a@gmail.com> (raw)
In-Reply-To: <cover.1743670253.git.nirjhar.roy.lists@gmail.com>


On 4/3/25 14:28, Nirjhar Roy (IBM) wrote:
> This series introduces "-q <n>" option to support unconditional looping.
> Along with this, it also brings some improvements to output data both, in stdout
> and in result.log.
>
> -q <n> option can be useful for fast unconditional looping (compared to
> -I <n>) to test a certain flakey test and get it's pass/fail metrics.
>
> This is similar to -L <n>, although with -L the test only loops if it
> fails the 1st time.
> The individual patches can provide more details about other changes and
> improvements.

Can I please get some reviews on this patch series?

--NR

>
> [v1] -> [v2]
>   1. This patch series removes the central config fs feature from [v1] (patch 4
>      patch 5) so that this can be reviewed separately. No functional changes.
>   2. Added R.B tag of Darrick is patch  1/5.
>
> [v1] https://lore.kernel.org/all/cover.1736496620.git.nirjhar.roy.lists@gmail.com/
>
> Nirjhar Roy (IBM) (3):
>    tests/selftest: Add a new pseudo flaky test.
>    check: Add -q <n> option to support unconditional looping.
>    check: Improve pass/fail metrics and section config output
>
>   check                  | 113 ++++++++++++++++++++++++++++++-----------
>   tests/selftest/007     |  21 ++++++++
>   tests/selftest/007.out |   2 +
>   3 files changed, 105 insertions(+), 31 deletions(-)
>   create mode 100755 tests/selftest/007
>   create mode 100644 tests/selftest/007.out
>
> --
> 2.34.1
>
-- 
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore


      parent reply	other threads:[~2025-04-09 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  8:58 [PATCH v2 0/3] Add support for -q <n> unconditional loop Nirjhar Roy (IBM)
2025-04-03  8:58 ` [PATCH v2 1/3] tests/selftest: Add a new pseudo flaky test Nirjhar Roy (IBM)
2025-04-03  8:58 ` [PATCH v2 2/3] check: Add -q <n> option to support unconditional looping Nirjhar Roy (IBM)
2025-04-13 21:48   ` Theodore Ts'o
2025-04-15  7:32     ` Nirjhar Roy (IBM)
2025-04-15 23:28       ` Dave Chinner
2025-04-23  6:02         ` Nirjhar Roy (IBM)
2025-04-15  9:06     ` Ritesh Harjani
2025-04-03  8:58 ` [PATCH v2 3/3] check: Improve pass/fail metrics and section config output Nirjhar Roy (IBM)
2025-04-09 16:34 ` Nirjhar Roy (IBM) [this message]

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=5fe56381-72c4-41ed-a4b6-d13eff1e427a@gmail.com \
    --to=nirjhar.roy.lists@gmail.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    --cc=zlang@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