From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v2 0/1] t6042: fix breakage on Windows
Date: Thu, 17 Jan 2019 00:29:20 -0800 (PST) [thread overview]
Message-ID: <pull.109.v2.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.109.git.gitgitgadget@gmail.com>
Unfortunately, Travis decided to change some things under the hood that
affect the Windows build. As a consequence, master has not been tested in
quite a while, even if the test runs pretended that it had been tested :-(
So imagine my surprise when master simply would refuse to pass the test
suite cleanly outside Travis, always failing at t6042, despite the fact that
Travis passed.
It turns out that two files are written too quickly in succession, running
into the issue where Git for Windows chooses not to populate the inode and
device numbers in the stat data (this is a noticeable performance
optimization). As a consequence, Git thinks the file is unchanged, and fails
to pick up a modification. And no, we cannot simply undo the performance
optimization, it would make things prohibitively slow in particular in large
worktrees, and it is not like the bug is likely to be hit in reality: for
Git to be fooled into thinking that a file is unchanged, it has to be
written with the same file size, and within a 100ns time bucket (it is
pretty improbable that there is any real-world scenario that would run into
that, except of course our regression test suite).
This patch works around this issue by forcing Git to recognize the new file
versions as new files (which they really are: the patch simply replaces
git mv <old> <new> && mv <file> <new> && git add <new>`
by
git rm <old> && mv <file> <new> && git add <new>`
which is not shorter, but even a performance improvement (an unnoticeable
one, of course).
Changes since v1:
* Clarified the change in the commit message.
Johannes Schindelin (1):
t6042: work around speed optimization on Windows
t/t6042-merge-rename-corner-cases.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
base-commit: 77556354bb7ac50450e3b28999e3576969869068
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-109%2Fdscho%2Ffix-t6042-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-109/dscho/fix-t6042-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/109
Range-diff vs v1:
1: 598de6652c ! 1: 55b0a641d4 t6042: work around speed optimization on Windows
@@ -35,6 +35,12 @@
now add the files as new files (as opposed to existing, just renamed
files).
+ Functionally, we do not change anything because we replace two `git mv
+ <old> <new>` calls (where `<new>` is completely overwritten and `git
+ add`ed later anyway) by `git rm <old>` calls (removing other files, too,
+ that are also completely overwritten and `git add`ed later).
+
+ Reviewed-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
diff --git a/t/t6042-merge-rename-corner-cases.sh b/t/t6042-merge-rename-corner-cases.sh
--
gitgitgadget
next prev parent reply other threads:[~2019-01-17 8:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 13:37 [PATCH 0/1] t6042: fix breakage on Windows Johannes Schindelin via GitGitGadget
2019-01-16 13:37 ` [PATCH 1/1] t6042: work around speed optimization " Johannes Schindelin via GitGitGadget
2019-01-16 15:56 ` Elijah Newren
2019-01-16 20:30 ` Johannes Schindelin
2019-01-16 21:13 ` Elijah Newren
2019-01-17 9:35 ` Johannes Schindelin
2019-01-16 15:32 ` [PATCH 0/1] t6042: fix breakage " Elijah Newren
2019-01-16 20:41 ` Johannes Schindelin
2019-01-17 8:29 ` Johannes Schindelin via GitGitGadget [this message]
2019-01-17 8:29 ` [PATCH v2 1/1] t6042: work around speed optimization " Johannes Schindelin via GitGitGadget
2019-01-17 20:57 ` Junio C Hamano
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=pull.109.v2.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
/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).