fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <anna@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] Improvements for NFS
Date: Tue,  8 Feb 2022 16:52:28 -0500	[thread overview]
Message-ID: <20220208215232.491780-1-anna@kernel.org> (raw)

From: Anna Schumaker <Anna.Schumaker@Netapp.com>

This is a collection of fixes that I've had in my private xfstests
instance on my NFS client VM for testing.

 I've been using the "-R xunit" option lately, so the first patch fixes up 
the PLATFORM and CHECK_OPTIONS output in the resulting xunit file. I
wouldn't be surprised if there is a better way to do this, so please let
me know!

The second patch moves a very long running test (generic/531) out of the
quick group because I'm tired of killing it after a half hour. Maybe
it's quick on non networked filesystems, though? I had some other ideas
on how to fix my issue that I included in the patch description.

The last two patches add some extra checks for functionality that NFS
doesn't support, otherwise the tests are getting marked as "failed" with
"whatever isn't supposted" in the test output log. After these patches
the tests are simply skipped.

Thoughts?

Anna


Anna Schumaker (4):
  check: Export CHECK_OPTIONS and PLATFORM for Xunit Reporting
  generic/531: Move test from 'quick' group to 'stress'
  generic/578: Test that filefrag is supported before running
  generic/633: Check if idmapped mounts are supported before running

 check             |  2 ++
 common/rc         | 14 ++++++++++++++
 tests/generic/531 |  2 +-
 tests/generic/578 |  2 +-
 tests/generic/633 |  1 +
 5 files changed, 19 insertions(+), 2 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-02-08 22:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 21:52 Anna Schumaker [this message]
2022-02-08 21:52 ` [PATCH 1/4] check: Export CHECK_OPTIONS and PLATFORM for Xunit Reporting Anna Schumaker
2022-02-08 21:52 ` [PATCH 2/4] generic/531: Move test from 'quick' group to 'stress' Anna Schumaker
2022-02-23 16:54   ` Darrick J. Wong
2022-02-23 19:38     ` Anna Schumaker
2022-02-24  4:14       ` Darrick J. Wong
2022-02-08 21:52 ` [PATCH 3/4] generic/578: Test that filefrag is supported before running Anna Schumaker
2022-02-23 16:57   ` Darrick J. Wong
2022-02-23 18:24     ` Anna Schumaker
2022-02-24  4:15       ` Darrick J. Wong
2022-02-08 21:52 ` [PATCH 4/4] generic/633: Check if idmapped mounts are " Anna Schumaker
2022-02-19  8:40   ` Su Yue

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=20220208215232.491780-1-anna@kernel.org \
    --to=anna@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).