git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* [PATCH] t4130: work around Windows limitation
@ 2016-07-27 12:39 Johannes Schindelin
  2016-07-27 16:37 ` Johannes Sixt
  0 siblings, 1 reply; 8+ messages in thread
From: Johannes Schindelin @ 2016-07-27 12:39 UTC (permalink / raw)
  To: git; +Cc: Junio C Hamano

On Windows, it is already pretty expensive to try to recreate the stat()
data that Git assumes is cheap to obtain. To make things halfway decent
in performance, we even have to skip emulating the inode and to
determine the number of hard links.

This is not a huge problem, usually, as either the size or the mtime or
the ctime are tell-tale enough to say when a file has changed, and even
if not, those changes are typically made after the index file was
written, triggering a rehashing of the files' contents.

The t4130-apply-criss-cross-rename test case, however, requires the
inode to determine that files of equal size were swapped, as renaming
files does not update their mtime. And even if we use
nanosecond-precision mtimes on Windows, the file system's time
granularity is typically much coarser (100ms for NTFS, 2s for FAT).

That means that every once in a while, t4130 fails on Windows.

This patch provides the work-around by pretending that the index file
was written earlier than it actually was.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
Published-As: https://github.com/dscho/git/releases/tag/t4130-mingw-v1
 t/t4130-apply-criss-cross-rename.sh | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/t/t4130-apply-criss-cross-rename.sh b/t/t4130-apply-criss-cross-rename.sh
index d173acd..ee91af8 100755
--- a/t/t4130-apply-criss-cross-rename.sh
+++ b/t/t4130-apply-criss-cross-rename.sh
@@ -29,6 +29,14 @@ test_expect_success 'criss-cross rename' '
 '
 
 test_expect_success 'diff -M -B' '
+	if test_have_prereq MINGW
+	then
+		# On Windows it is prohbitively expensive to retrieve the
+		# equivalent of an "inode" when calling stat(), therefore we
+		# rely on mtime/ctime/size changes to let us know whether a
+		# file has changed, including the mtime relative to the index.
+		test-chmtime -1 .git/index
+	fi &&
 	git diff -M -B > diff &&
 	git reset --hard
 
@@ -52,6 +60,14 @@ test_expect_success 'criss-cross rename' '
 '
 
 test_expect_success 'diff -M -B' '
+	if test_have_prereq MINGW
+	then
+		# On Windows it is prohbitively expensive to retrieve the
+		# equivalent of an "inode" when calling stat(), therefore we
+		# rely on mtime/ctime/size changes to let us know whether a
+		# file has changed, including the mtime relative to the index.
+		test-chmtime -1 .git/index
+	fi &&
 	git diff -M -B > diff &&
 	git reset --hard
 '
-- 
2.9.0.281.g286a8d9

base-commit: 8c6d1f9807c67532e7fb545a944b064faff0f70b

^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [PATCH] t4130: work around Windows limitation
  2016-07-27 12:39 [PATCH] t4130: work around Windows limitation Johannes Schindelin
@ 2016-07-27 16:37 ` Johannes Sixt
  2016-07-27 16:40   ` Junio C Hamano
  0 siblings, 1 reply; 8+ messages in thread
From: Johannes Sixt @ 2016-07-27 16:37 UTC (permalink / raw)
  To: Johannes Schindelin; +Cc: git, Junio C Hamano

Am 27.07.2016 um 14:39 schrieb Johannes Schindelin:
> On Windows, it is already pretty expensive to try to recreate the stat()
> data that Git assumes is cheap to obtain. To make things halfway decent
> in performance, we even have to skip emulating the inode and to
> determine the number of hard links.
> 
> This is not a huge problem, usually, as either the size or the mtime or
> the ctime are tell-tale enough to say when a file has changed, and even
> if not, those changes are typically made after the index file was
> written, triggering a rehashing of the files' contents.
> 
> The t4130-apply-criss-cross-rename test case, however, requires the
> inode to determine that files of equal size were swapped, as renaming
> files does not update their mtime. And even if we use
> nanosecond-precision mtimes on Windows, the file system's time
> granularity is typically much coarser (100ms for NTFS, 2s for FAT).
> 
> That means that every once in a while, t4130 fails on Windows.
> 
> This patch provides the work-around by pretending that the index file
> was written earlier than it actually was.
> 
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
> Published-As: https://github.com/dscho/git/releases/tag/t4130-mingw-v1
>  t/t4130-apply-criss-cross-rename.sh | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/t/t4130-apply-criss-cross-rename.sh b/t/t4130-apply-criss-cross-rename.sh
> index d173acd..ee91af8 100755
> --- a/t/t4130-apply-criss-cross-rename.sh
> +++ b/t/t4130-apply-criss-cross-rename.sh
> @@ -29,6 +29,14 @@ test_expect_success 'criss-cross rename' '
>  '
>  
>  test_expect_success 'diff -M -B' '
> +	if test_have_prereq MINGW
> +	then
> +		# On Windows it is prohbitively expensive to retrieve the
> +		# equivalent of an "inode" when calling stat(), therefore we
> +		# rely on mtime/ctime/size changes to let us know whether a
> +		# file has changed, including the mtime relative to the index.
> +		test-chmtime -1 .git/index
> +	fi &&
>  	git diff -M -B > diff &&
>  	git reset --hard
>  
> @@ -52,6 +60,14 @@ test_expect_success 'criss-cross rename' '
>  '
>  
>  test_expect_success 'diff -M -B' '
> +	if test_have_prereq MINGW
> +	then
> +		# On Windows it is prohbitively expensive to retrieve the
> +		# equivalent of an "inode" when calling stat(), therefore we
> +		# rely on mtime/ctime/size changes to let us know whether a
> +		# file has changed, including the mtime relative to the index.
> +		test-chmtime -1 .git/index
> +	fi &&
>  	git diff -M -B > diff &&
>  	git reset --hard
>  '
> 

How about this instead? It makes the sizes of the files different,
which is a bit less obscure, IMHO.

---- 8< ----
[PATCH] t4130: work around Windows limitation

On Windows, it is already pretty expensive to try to recreate the stat()
data that Git assumes is cheap to obtain. To make things halfway decent
in performance, we even have to skip emulating the inode and to
determine the number of hard links.

This is not a huge problem, usually, as either the size or the mtime or
the ctime are tell-tale enough to say when a file has changed, and even
if not, those changes are typically made after the index file was
written, triggering a rehashing of the files' contents.

The t4130-apply-criss-cross-rename test case, however, requires the
inode to determine that files of equal size were swapped, as renaming
files does not update their mtime. Every once in a while, t4130 fails
on Windows of this missing piece.

Equal file sizes are not crucial for the test cases, however. Hence,
generate files with different sizes so that there is some property that
the swapped files can be discovered reliably even on Windows.

Helped-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
---
 t/t4130-apply-criss-cross-rename.sh | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/t/t4130-apply-criss-cross-rename.sh b/t/t4130-apply-criss-cross-rename.sh
index d173acd..f8a313b 100755
--- a/t/t4130-apply-criss-cross-rename.sh
+++ b/t/t4130-apply-criss-cross-rename.sh
@@ -13,9 +13,13 @@ create_file() {
 }
 
 test_expect_success 'setup' '
-	create_file file1 "File1 contents" &&
-	create_file file2 "File2 contents" &&
-	create_file file3 "File3 contents" &&
+	# Ensure that file sizes are different, because on Windows
+	# lstat() does not discover inode numbers, and we need
+	# other properties to discover swapped files
+	# (mtime is not always different, either).
+	create_file file1 "some content" &&
+	create_file file2 "some other content" &&
+	create_file file3 "again something else" &&
 	git add file1 file2 file3 &&
 	git commit -m 1
 '
-- 
2.9.0.443.ga8520ad


^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [PATCH] t4130: work around Windows limitation
  2016-07-27 16:37 ` Johannes Sixt
@ 2016-07-27 16:40   ` Junio C Hamano
  2016-07-30  8:11     ` Johannes Schindelin
  0 siblings, 1 reply; 8+ messages in thread
From: Junio C Hamano @ 2016-07-27 16:40 UTC (permalink / raw)
  To: Johannes Sixt; +Cc: Johannes Schindelin, Git Mailing List

On Wed, Jul 27, 2016 at 9:37 AM, Johannes Sixt <j6t@kdbg.org> wrote:
>
> How about this instead? It makes the sizes of the files different,
> which is a bit less obscure, IMHO.
> ...
> Equal file sizes are not crucial for the test cases, however.

That does sounds like a better solution.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] t4130: work around Windows limitation
  2016-07-27 16:40   ` Junio C Hamano
@ 2016-07-30  8:11     ` Johannes Schindelin
  2016-08-03  6:15       ` [PATCH v2] " Johannes Sixt
  0 siblings, 1 reply; 8+ messages in thread
From: Johannes Schindelin @ 2016-07-30  8:11 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: Johannes Sixt, Git Mailing List

Hi,

On Wed, 27 Jul 2016, Junio C Hamano wrote:

> On Wed, Jul 27, 2016 at 9:37 AM, Johannes Sixt <j6t@kdbg.org> wrote:
> >
> > How about this instead? It makes the sizes of the files different,
> > which is a bit less obscure, IMHO.
> > ...
> > Equal file sizes are not crucial for the test cases, however.
> 
> That does sounds like a better solution.

Fine by me.

Thanks,
Dscho

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [PATCH v2] t4130: work around Windows limitation
  2016-07-30  8:11     ` Johannes Schindelin
@ 2016-08-03  6:15       ` Johannes Sixt
  2016-08-03 12:03         ` Johannes Schindelin
  2016-08-03 15:50         ` Junio C Hamano
  0 siblings, 2 replies; 8+ messages in thread
From: Johannes Sixt @ 2016-08-03  6:15 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: Johannes Schindelin, Git Mailing List

On Windows, it is already pretty expensive to try to recreate the stat()
data that Git assumes is cheap to obtain. To make things halfway decent
in performance, we even have to skip emulating the inode and to
determine the number of hard links.

This is not a huge problem, usually, as either the size or the mtime or
the ctime are tell-tale enough to say when a file has changed, and even
if not, those changes are typically made after the index file was
written, triggering a rehashing of the files' contents.

The t4130-apply-criss-cross-rename test case, however, requires the
inode to determine that files of equal size were swapped, as renaming
files does not update their mtime. Every once in a while, t4130 fails
on Windows because of this missing piece.

Equal file sizes are not crucial for the test cases, however. Hence,
generate files with different sizes so that there is some property that
the swapped files can be discovered reliably even on Windows.

Helped-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
---
 This fell through the cracks, I think. I marked it as v2 because
 there is a minor fixup in the commit message.

 t/t4130-apply-criss-cross-rename.sh | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/t/t4130-apply-criss-cross-rename.sh b/t/t4130-apply-criss-cross-rename.sh
index d173acd..f8a313b 100755
--- a/t/t4130-apply-criss-cross-rename.sh
+++ b/t/t4130-apply-criss-cross-rename.sh
@@ -13,9 +13,13 @@ create_file() {
 }
  test_expect_success 'setup' '
-	create_file file1 "File1 contents" &&
-	create_file file2 "File2 contents" &&
-	create_file file3 "File3 contents" &&
+	# Ensure that file sizes are different, because on Windows
+	# lstat() does not discover inode numbers, and we need
+	# other properties to discover swapped files
+	# (mtime is not always different, either).
+	create_file file1 "some content" &&
+	create_file file2 "some other content" &&
+	create_file file3 "again something else" &&
 	git add file1 file2 file3 &&
 	git commit -m 1
 '
-- 
2.9.0.443.ga8520ad


^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [PATCH v2] t4130: work around Windows limitation
  2016-08-03  6:15       ` [PATCH v2] " Johannes Sixt
@ 2016-08-03 12:03         ` Johannes Schindelin
  2016-08-03 15:50         ` Junio C Hamano
  1 sibling, 0 replies; 8+ messages in thread
From: Johannes Schindelin @ 2016-08-03 12:03 UTC (permalink / raw)
  To: Johannes Sixt; +Cc: Junio C Hamano, Git Mailing List

Hi Hannes,

On Wed, 3 Aug 2016, Johannes Sixt wrote:

>  This fell through the cracks, I think. I marked it as v2 because
>  there is a minor fixup in the commit message.

It appears that it did fall through the cracks.

Given that it would make my life substantially easier (because I run the
test suite often enough to hit this edge case multiple times a day), I
would like to ask to fast-track it into v2.9.3.

Thanks,
Dscho

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH v2] t4130: work around Windows limitation
  2016-08-03  6:15       ` [PATCH v2] " Johannes Sixt
  2016-08-03 12:03         ` Johannes Schindelin
@ 2016-08-03 15:50         ` Junio C Hamano
  2016-08-04  5:31           ` Johannes Sixt
  1 sibling, 1 reply; 8+ messages in thread
From: Junio C Hamano @ 2016-08-03 15:50 UTC (permalink / raw)
  To: Johannes Sixt; +Cc: Johannes Schindelin, Git Mailing List

Johannes Sixt <j6t@kdbg.org> writes:

>  This fell through the cracks, I think. I marked it as v2 because
>  there is a minor fixup in the commit message.

Thanks.  The patch itself seems to got whitespace damaged somewhere
between you and me, which I fixed up, but there may be similar
damage to the proposed log message as well.  What I read may already
have whitespace damaged but I read the message twice and it made
sense to me, so let's assume all is well ;-)

Thanks.

>
>  t/t4130-apply-criss-cross-rename.sh | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/t/t4130-apply-criss-cross-rename.sh b/t/t4130-apply-criss-cross-rename.sh
> index d173acd..f8a313b 100755
> --- a/t/t4130-apply-criss-cross-rename.sh
> +++ b/t/t4130-apply-criss-cross-rename.sh
> @@ -13,9 +13,13 @@ create_file() {
>  }
>   test_expect_success 'setup' '
> -	create_file file1 "File1 contents" &&
> -	create_file file2 "File2 contents" &&
> -	create_file file3 "File3 contents" &&
> +	# Ensure that file sizes are different, because on Windows
> +	# lstat() does not discover inode numbers, and we need
> +	# other properties to discover swapped files
> +	# (mtime is not always different, either).
> +	create_file file1 "some content" &&
> +	create_file file2 "some other content" &&
> +	create_file file3 "again something else" &&
>  	git add file1 file2 file3 &&
>  	git commit -m 1
>  '

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH v2] t4130: work around Windows limitation
  2016-08-03 15:50         ` Junio C Hamano
@ 2016-08-04  5:31           ` Johannes Sixt
  0 siblings, 0 replies; 8+ messages in thread
From: Johannes Sixt @ 2016-08-04  5:31 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: Johannes Schindelin, Git Mailing List

Am 03.08.2016 um 17:50 schrieb Junio C Hamano:
> Johannes Sixt <j6t@kdbg.org> writes:
> The patch itself seems to got whitespace damaged somewhere
> between you and me, which I fixed up,

Sorry for the damaged patch. I forgot that Thunderbird's "Send again" 
feature as well as copying and pasting between Thunderbird windows is 
poison for patch text.

What you have queued in js/t4130-rename-without-ino is correct. Thank 
you very much!

-- Hannes


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2016-08-04  5:31 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-27 12:39 [PATCH] t4130: work around Windows limitation Johannes Schindelin
2016-07-27 16:37 ` Johannes Sixt
2016-07-27 16:40   ` Junio C Hamano
2016-07-30  8:11     ` Johannes Schindelin
2016-08-03  6:15       ` [PATCH v2] " Johannes Sixt
2016-08-03 12:03         ` Johannes Schindelin
2016-08-03 15:50         ` Junio C Hamano
2016-08-04  5:31           ` Johannes Sixt

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).