From: <rsbecker@nexbridge.com>
To: "'Chuck Lever'" <chuck.lever@oracle.com>, <git@vger.kernel.org>
Cc: <linux-nfs@vger.kernel.org>
Subject: RE: t0032 fails on NFS mounts
Date: Tue, 12 Mar 2024 13:11:15 -0400 [thread overview]
Message-ID: <0cb701da74a0$4e39ef60$eaadce20$@nexbridge.com> (raw)
In-Reply-To: <ZfBwZTL9zqDsac5m@manet.1015granger.net>
On Tuesday, March 12, 2024 11:10 AM, Chuck Lever wrote:
>I've checked out "maint".
>
>Unit test t0032 fails when run on an NFS mount:
>
>[vagrant@cel t]$ ./t0032-reftable-unittest.sh not ok 1 - unittests
>#
># TMPDIR=$(pwd) && export TMPDIR &&
># test-tool reftable
>#
># failed 1 among 1 test(s)
>1..1
>[vagrant@cel t]$
>
>But not on XFS:
>
>[vagrant@cel t]$ ./t0032-reftable-unittest.sh ok 1 - unittests # passed all
1 test(s)
>1..1
>[vagrant@cel t]$ cd ..
>[vagrant@cel git]$ ./git --version
>git version 2.44.0
>[vagrant@cel git]$
>
>v2.43.2 seems to work OK.
I have seen a similar effect on a standard POSIX file system (NonStop) when
run in a special platform container (Pathway). It does not happen for me
when run from bash directly. This may be something other than an NFS effect,
or unrelated to what I observed. I'll be monitoring this sub-test for
repeats.
--Randall
next prev parent reply other threads:[~2024-03-12 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 15:10 t0032 fails on NFS mounts Chuck Lever
2024-03-12 17:11 ` rsbecker [this message]
2024-03-21 15:50 ` Patrick Steinhardt
2024-03-13 7:20 ` Jeff King
2024-03-15 0:35 ` Patrick Steinhardt
2024-03-15 15:41 ` Junio C Hamano
2024-03-21 15:14 ` Patrick Steinhardt
2024-03-21 15:39 ` [PATCH] reftable: fix tests being broken by NFS' delete-after-close semantics Patrick Steinhardt
2024-03-21 17:35 ` Junio C Hamano
2024-03-22 15:15 ` Toon Claes
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='0cb701da74a0$4e39ef60$eaadce20$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=chuck.lever@oracle.com \
--cc=git@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).