Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jeff Layton <jlayton@kernel.org>
Date:   Thu, 31 Aug 2023 14:40:30 -0400
Subject: [PATCH fstests 3/3] generic/187: don't run this test on NFS
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <20230831-nfs-skip-v1-3-d54c1c6a9af2@kernel.org>
References: <20230831-nfs-skip-v1-0-d54c1c6a9af2@kernel.org>
In-Reply-To: <20230831-nfs-skip-v1-0-d54c1c6a9af2@kernel.org>
To:     fstests@vger.kernel.org
Cc:     linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>
Precedence: bulk

This test is unreliable on NFS. It fails consistently when run vs. a
server exporting btrfs, but passes when the server exports xfs. Since we
don't have any sort of attribute that we can require to test this, just
skip this one on NFS.

Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
 tests/generic/187 | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tests/generic/187 b/tests/generic/187
index 0653b92f12f4..05e609964a9d 100755
--- a/tests/generic/187
+++ b/tests/generic/187
@@ -36,6 +36,9 @@ _require_xfs_io_command "fpunch"
 test $FSTYP = "btrfs" && _notrun "Can't fragment free space on btrfs."
 _require_odirect
 
+# This test is unreliable on NFS, as it depends on the exported filesystem.
+test $FSTYP = "nfs" && _notrun "This test is unreliable on NFS"
+
 _fragment_freesp()
 {
 	file=$1

-- 
2.41.0