linux-ext4.vger.kernel.org archive mirror
 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, nirjhar.roy.lists@gmail.com
Subject: [RFC 0/5] Add support for central fsconfig and -q <n> unconditional loop
Date: Fri, 10 Jan 2025 09:10:24 +0000	[thread overview]
Message-ID: <cover.1736496620.git.nirjhar.roy.lists@gmail.com> (raw)

This series introduces 2 new features, central fsconfig support and "-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.
Central fsconfig feature allows us to define MKFS and MOUNT options for
different filesystems and use this central config to invoke any test.
We don't need to maintain different sections in local.config file for
different mkfs and mount options of any given FS.
e.g.
./check -c configs/xfs/4k,configs/ext4/1k -g quick

Central fsconfigs can be useful for below reasons:-
1. Testers and other FS developers can know what is being actively
tested and maintained by FS Maintainers.
2. It "reduces" the need to maintain different local.config files or
different sections within local.config file for subsystem maintainers
for testing different filesystem configurations.
-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.

This is something that was discussed during last LSFMM [1]
[1] https://lore.kernel.org/all/87h6h4sopf.fsf@doe.com/

Nirjhar Roy (IBM) (5):
  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,common/config: Add support for central fsconfig
  configs: Add a couple of xfs and ext4 configuration templates.

 README.config-sections |  12 +++
 check                  | 193 +++++++++++++++++++++++++++++++----------
 common/config          |  51 ++++++++++-
 common/report          |   2 +-
 configs/ext4/1k        |   3 +
 configs/ext4/4k        |   3 +
 configs/ext4/64k       |   3 +
 configs/xfs/1k         |   3 +
 configs/xfs/4k         |   3 +
 configs/xfs/64k        |   3 +
 configs/xfs/adv        |   3 +
 configs/xfs/quota      |   3 +
 tests/selftest/007     |  21 +++++
 tests/selftest/007.out |   2 +
 14 files changed, 256 insertions(+), 49 deletions(-)
 create mode 100644 configs/ext4/1k
 create mode 100644 configs/ext4/4k
 create mode 100644 configs/ext4/64k
 create mode 100644 configs/xfs/1k
 create mode 100644 configs/xfs/4k
 create mode 100644 configs/xfs/64k
 create mode 100644 configs/xfs/adv
 create mode 100644 configs/xfs/quota
 create mode 100755 tests/selftest/007
 create mode 100644 tests/selftest/007.out

--
2.34.1


             reply	other threads:[~2025-01-10  9:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  9:10 Nirjhar Roy (IBM) [this message]
2025-01-10  9:10 ` [RFC 1/5] tests/selftest: Add a new pseudo flaky test Nirjhar Roy (IBM)
2025-01-13 16:46   ` Darrick J. Wong
2025-01-10  9:10 ` [RFC 2/5] check: Add -q <n> option to support unconditional looping Nirjhar Roy (IBM)
2025-01-10 16:08   ` Theodore Ts'o
2025-01-11  3:35     ` Ritesh Harjani
2025-01-10  9:10 ` [RFC 3/5] check: Improve pass/fail metrics and section config output Nirjhar Roy (IBM)
2025-01-10  9:10 ` [RFC 4/5] check,common/config: Add support for central fsconfig Nirjhar Roy (IBM)
2025-01-10 16:38   ` Theodore Ts'o
2025-02-20  9:56   ` Anand Jain
2025-03-01 17:30     ` Ritesh Harjani
2025-03-03  9:30       ` Anand Jain
2025-01-10  9:10 ` [RFC 5/5] configs: Add a couple of xfs and ext4 configuration templates Nirjhar Roy (IBM)

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=cover.1736496620.git.nirjhar.roy.lists@gmail.com \
    --to=nirjhar.roy.lists@gmail.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;
as well as URLs for NNTP newsgroup(s).