[v2,6/8] t7063: disable fsmonitor with status cache
diff mbox series

Message ID 9cd4a08d82521082f0ee13ebea353708fada3403.1575907804.git.gitgitgadget@gmail.com
State New
Headers show
  • Improve testability with GIT_TEST_FSMONITOR
Related show

Commit Message

Han-Wen Nienhuys via GitGitGadget Dec. 9, 2019, 4:10 p.m. UTC
From: Derrick Stolee <dstolee@microsoft.com>

The fsmonitor feature allows an external tool such as watchman to
monitor the working directory. The direct test
t7619-status-fsmonitor.sh provides some coverage, but it would be
better to run the entire test suite with watchman enabled. This
would provide more confidence that the feature is working as

The status cache tests use GIT_TRACE_UNTRACKED_STATS to check very
detailed statistics related to how much Git actually checked for
untracked files. The fsmonitor feature changes the expected behavior
here, so disable the GIT_TEST_FSMONITOR environment variable.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
 t/t7063-status-untracked-cache.sh | 3 +++
 1 file changed, 3 insertions(+)

diff mbox series

diff --git a/t/t7063-status-untracked-cache.sh b/t/t7063-status-untracked-cache.sh
index 190ae149cf..c433738a3a 100755
--- a/t/t7063-status-untracked-cache.sh
+++ b/t/t7063-status-untracked-cache.sh
@@ -4,6 +4,9 @@  test_description='test untracked cache'
 . ./test-lib.sh
+# fsmonitor changes the expected behvaior of GIT_TRACE_UNTRACKED_STATS
 # On some filesystems (e.g. FreeBSD's ext2 and ufs) directory mtime
 # is updated lazily after contents in the directory changes, which
 # forces the untracked cache code to take the slow path.  A test