From: Stefan Beller <sbeller@google.com>
To: Elijah Newren <newren@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH 04/30] directory rename detection: basic testcases
Date: Mon, 13 Nov 2017 14:04:35 -0800 [thread overview]
Message-ID: <CAGZ79kbmt7jt13D-HY90+LBaCHsqvDOYnrmJ41hR3YsgEceirg@mail.gmail.com> (raw)
In-Reply-To: <20171110190550.27059-5-newren@gmail.com>
On Fri, Nov 10, 2017 at 11:05 AM, Elijah Newren <newren@gmail.com> wrote:
> Signed-off-by: Elijah Newren <newren@gmail.com>
> ---
> t/t6043-merge-rename-directories.sh | 391 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 391 insertions(+)
> create mode 100755 t/t6043-merge-rename-directories.sh
>
> diff --git a/t/t6043-merge-rename-directories.sh b/t/t6043-merge-rename-directories.sh
> new file mode 100755
> index 0000000000..b737b0a105
> --- /dev/null
> +++ b/t/t6043-merge-rename-directories.sh
> @@ -0,0 +1,391 @@
> +#!/bin/sh
> +
> +test_description="recursive merge with directory renames"
> +# includes checking of many corner cases, with a similar methodology to:
> +# t6042: corner cases with renames but not criss-cross merges
> +# t6036: corner cases with both renames and criss-cross merges
> +#
> +# The setup for all of them, pictorially, is:
> +#
> +# B
> +# o
> +# / \
> +# A o ?
> +# \ /
> +# o
> +# C
> +#
> +# To help make it easier to follow the flow of tests, they have been
> +# divided into sections and each test will start with a quick explanation
> +# of what commits A, B, and C contain.
> +#
> +# Notation:
> +# z/{b,c} means files z/b and z/c both exist
> +# x/d_1 means file x/d exists with content d1. (Purpose of the
> +# underscore notation is to differentiate different
> +# files that might be renamed into each other's paths.)
> +
> +. ./test-lib.sh
> +
> +
> +###########################################################################
> +# SECTION 1: Basic cases we should be able to handle
> +###########################################################################
> +
> +# Testcase 1a, Basic directory rename.
> +# Commit A: z/{b,c}
> +# Commit B: y/{b,c}
> +# Commit C: z/{b,c,d,e/f}
(minor thought:)
After rereading the docs above this is clear; I wonder if instead of A, B, C
a notation of Base, ours, theirs would be easier to understand?
> +test_expect_success '1a-setup: Simple directory rename detection' '
> +test_expect_failure '1a-check: Simple directory rename detection' '
Thanks for splitting the setup and the check into two different test cases!
> + git checkout B^0 &&
Any reason for ^0 ? (to make clear it is a branch?)
> +# Testcase 1b, Merge a directory with another
> +# Commit A: z/{b,c}, y/d
> +# Commit B: z/{b,c,e}, y/d
> +# Commit C: y/{b,c,d}
> +# Expected: y/{b,c,d,e}
> +
> +test_expect_success '1b-setup: Merge a directory with another' '
> + git rm -rf . &&
> + git clean -fdqx &&
> + rm -rf .git &&
> + git init &&
This is quite a strong statement to start a test with.
Nowadays we rather do
test_when_finished "some command" &&
than polluting the follow up tests. But as you split up the previous test
into 2 tests, it is not clear if this would bring any good.
Also these are four cleanup commands, I'd have expected fewer.
Maybe just "rm -rf ." ? Or as we make a new repo for each test case,
test_create_repo 1a &&
cd 1a
in the first setup, and here we do
test_create_repo 1b &&
cd 1b
relying on test_done to cleanup everything afterwards?
> +# Testcase 1c, Transitive renaming
> +# (Related to testcases 3a and 6d -- when should a transitive rename apply?)
> +# (Related to testcases 9c and 9d -- can transitivity repeat?)
> +# Commit A: z/{b,c}, x/d
> +# Commit B: y/{b,c}, x/d
> +# Commit C: z/{b,c,d}
So B is "Rename z to y" and C is "Move x/d to z/d"
> +# Expected: y/{b,c,d} (because x/d -> z/d -> y/d)
This is an excellent expectation for a clean case like this.
I have not reached 3, 9 yet, so I'll remember these questions.
> +test_expect_success '1c-setup: Transitive renaming' '
> + git rm -rf . &&
> + git clean -fdqx &&
> + rm -rf .git &&
> + git init &&
> +
> + mkdir z &&
> + echo b >z/b &&
> + echo c >z/c &&
> + mkdir x &&
> + echo d >x/d &&
> + git add z x &&
> + test_tick &&
> + git commit -m "A" &&
> +
> + git branch A &&
> + git branch B &&
> + git branch C &&
> +
> + git checkout B &&
> + git mv z y &&
> + test_tick &&
> + git commit -m "B" &&
> +
> + git checkout C &&
> + git mv x/d z/d &&
> + test_tick &&
> + git commit -m "C"
> +'
> +
> +test_expect_failure '1c-check: Transitive renaming' '
> + git checkout B^0 &&
> +
> + git merge -s recursive C^0 &&
> +
> + test 3 -eq $(git ls-files -s | wc -l) &&
git ls-files >out &&
test_line_count = 3 out &&
maybe? Piping output of git commands somewhere is an
anti-pattern as we cannot examine the return code of ls-files in this case.
> + test $(git rev-parse HEAD:y/b) = $(git rev-parse A:z/b) &&
> + test $(git rev-parse HEAD:y/c) = $(git rev-parse A:z/c) &&
> + test $(git rev-parse HEAD:y/d) = $(git rev-parse A:x/d) &&
Speaking of these, there are quite a lot of invocations of rev-parse,
though it looks clean; recently Junio had some good ideas regarding a
similar test[1].
So maybe
git rev-parse >actual \
HEAD:y/b HEAD:y/c HEAD:y/d &&
git rev-parse >expect \
A:z/b A:z/c A:x/d &&
test_cmp expect actual
Not sure if that is any nicer, but has fewer calls.
[1] https://public-inbox.org/git/xmqqa807ztx4.fsf@gitster.mtv.corp.google.com/
> + test_must_fail git rev-parse HEAD:x/d &&
> + test_must_fail git rev-parse HEAD:z/d &&
> + test ! -f z/d
> +'
> +
> +# Testcase 1d, Directory renames (merging two directories into one new one)
> +# cause a rename/rename(2to1) conflict
> +# (Related to testcases 1c and 7b)
> +# Commit A. z/{b,c}, y/{d,e}
> +# Commit B. x/{b,c}, y/{d,e,m,wham}
> +# Commit C. z/{b,c,n,wham}, x/{d,e}
> +# Expected: x/{b,c,d,e,m,n}, CONFLICT:(y/wham & z/wham -> x/wham)
> +# Note: y/m & z/n should definitely move into x. By the same token, both
> +# y/wham & z/wham should to...giving us a conflict.
If wham are equal (in oid), shouldn't this not conflict and only conflict
when z/wham and x/wham differ in oid, but have the same sub-path?
> +
> +# Testcase 1e, Renamed directory, with all filenames being renamed too
> +# Commit A: z/{oldb,oldc}
> +# Commit B: y/{newb,newc}
> +# Commit C: z/{oldb,oldc,d}
What about oldd ?
(expecting a pattern across many files of s/old/new/ isn't unreasonable,
but maybe too much for now?)
By having no "old" prefix there is only one thing to do, which is y/d
> +# Expected: y/{newb,newc,d}
ok.
> +# Testcase 1f, Split a directory into two other directories
> +# (Related to testcases 3a, all of section 2, and all of section 4)
> +# Commit A: z/{b,c,d,e,f}
> +# Commit B: z/{b,c,d,e,f,g}
> +# Commit C: y/{b,c}, x/{d,e,f}
> +# Expected: y/{b,c}, x/{d,e,f,g}
Why not y/g ? Because there are more files in x?
I can come up with a reasonable counter example:
A: src/{main.c, foo.c, bar.c, magic.py}
B: src/{main.c, foo.c, bar.c, magic.py, magic-helper.py}
C: src/{main.c, foo.c, bar.c} py/{magic.py}
Expect: src/{main.c, foo.c, bar.c} py/{magic.py, magic-helper.py}
> +
> +###########################################################################
> +# Rules suggested by testcases in section 1:
> +#
> +# We should still detect the directory rename even if it wasn't just
> +# the directory renamed, but the files within it. (see 1b)
> +#
> +# If renames split a directory into two or more others, the directory
> +# with the most renames, "wins" (see 1c). However, see the testcases
> +# in section 2, plus testcases 3a and 4a.
oh, ok. I presume testcases 2 follows in a later patch.
I'll go looking.
Thanks,
Stefan
next prev parent reply other threads:[~2017-11-13 22:04 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 19:05 [PATCH 00/30] Add directory rename detection to git Elijah Newren
2017-11-10 19:05 ` [PATCH 01/30] Tighten and correct a few testcases for merging and cherry-picking Elijah Newren
2017-11-13 19:32 ` Stefan Beller
2017-11-10 19:05 ` [PATCH 02/30] merge-recursive: Fix logic ordering issue Elijah Newren
2017-11-13 19:48 ` Stefan Beller
2017-11-13 22:04 ` Elijah Newren
2017-11-13 22:12 ` Stefan Beller
2017-11-13 23:39 ` Elijah Newren
2017-11-13 23:46 ` Stefan Beller
2017-11-10 19:05 ` [PATCH 03/30] merge-recursive: Add explanation for src_entry and dst_entry Elijah Newren
2017-11-13 21:06 ` Stefan Beller
2017-11-13 22:57 ` Elijah Newren
2017-11-13 23:11 ` Stefan Beller
2017-11-14 1:26 ` Junio C Hamano
2017-11-10 19:05 ` [PATCH 04/30] directory rename detection: basic testcases Elijah Newren
2017-11-13 22:04 ` Stefan Beller [this message]
2017-11-14 0:57 ` Elijah Newren
2017-11-14 1:21 ` Stefan Beller
2017-11-14 1:40 ` Elijah Newren
2017-11-14 2:03 ` Junio C Hamano
2017-11-10 19:05 ` [PATCH 05/30] directory rename detection: directory splitting testcases Elijah Newren
2017-11-13 23:20 ` Stefan Beller
2017-11-10 19:05 ` [PATCH 06/30] directory rename detection: testcases to avoid taking detection too far Elijah Newren
2017-11-13 23:25 ` Stefan Beller
2017-11-14 1:02 ` Elijah Newren
2017-11-10 19:05 ` [PATCH 07/30] directory rename detection: partially renamed directory testcase/discussion Elijah Newren
2017-11-14 0:07 ` Stefan Beller
2017-11-10 19:05 ` [PATCH 08/30] directory rename detection: files/directories in the way of some renames Elijah Newren
2017-11-14 0:15 ` Stefan Beller
2017-11-14 1:19 ` Elijah Newren
2017-11-10 19:05 ` [PATCH 09/30] directory rename detection: testcases checking which side did the rename Elijah Newren
2017-11-14 0:25 ` Stefan Beller
2017-11-14 1:30 ` Elijah Newren
2017-11-10 19:05 ` [PATCH 10/30] directory rename detection: more involved edge/corner testcases Elijah Newren
2017-11-14 0:42 ` Stefan Beller
2017-11-14 21:11 ` Elijah Newren
2017-11-14 22:47 ` Stefan Beller
2017-11-10 19:05 ` [PATCH 11/30] directory rename detection: testcases exploring possibly suboptimal merges Elijah Newren
2017-11-14 20:33 ` Stefan Beller
2017-11-14 21:42 ` Elijah Newren
2017-11-10 19:05 ` [PATCH 12/30] directory rename detection: miscellaneous testcases to complete coverage Elijah Newren
2017-11-15 20:03 ` Stefan Beller
2017-11-16 21:17 ` Elijah Newren
2017-11-10 19:05 ` [PATCH 13/30] directory rename detection: tests for handling overwriting untracked files Elijah Newren
2017-11-10 19:05 ` [PATCH 14/30] directory rename detection: tests for handling overwriting dirty files Elijah Newren
2017-11-10 19:05 ` [PATCH 15/30] merge-recursive: Move the get_renames() function Elijah Newren
2017-11-14 4:46 ` Junio C Hamano
2017-11-14 17:41 ` Elijah Newren
2017-11-15 1:20 ` Junio C Hamano
2017-11-10 19:05 ` [PATCH 16/30] merge-recursive: Introduce new functions to handle rename logic Elijah Newren
2017-11-14 4:56 ` Junio C Hamano
2017-11-14 5:14 ` Junio C Hamano
2017-11-14 18:24 ` Elijah Newren
2017-11-10 19:05 ` [PATCH 17/30] merge-recursive: Fix leaks of allocated renames and diff_filepairs Elijah Newren
2017-11-14 4:58 ` Junio C Hamano
2017-11-10 19:05 ` [PATCH 18/30] merge-recursive: Make !o->detect_rename codepath more obvious Elijah Newren
2017-11-10 19:05 ` [PATCH 19/30] merge-recursive: Split out code for determining diff_filepairs Elijah Newren
2017-11-14 5:20 ` Junio C Hamano
2017-11-10 19:05 ` [PATCH 20/30] merge-recursive: Add a new hashmap for storing directory renames Elijah Newren
2017-11-10 19:05 ` [PATCH 21/30] merge-recursive: Add get_directory_renames() Elijah Newren
2017-11-14 5:30 ` Junio C Hamano
2017-11-14 18:38 ` Elijah Newren
2017-11-10 19:05 ` [PATCH 22/30] merge-recursive: Check for directory level conflicts Elijah Newren
2017-11-10 19:05 ` [PATCH 23/30] merge-recursive: Add a new hashmap for storing file collisions Elijah Newren
2017-11-10 19:05 ` [PATCH 24/30] merge-recursive: Add computation of collisions due to dir rename & merging Elijah Newren
2018-06-10 10:56 ` René Scharfe
2018-06-10 11:03 ` René Scharfe
2018-06-10 20:44 ` Jeff King
2018-06-11 15:03 ` Elijah Newren
2018-06-14 17:36 ` Junio C Hamano
2017-11-10 19:05 ` [PATCH 25/30] merge-recursive: Check for file level conflicts then get new name Elijah Newren
2017-11-10 19:05 ` [PATCH 26/30] merge-recursive: When comparing files, don't include trees Elijah Newren
2017-11-10 19:05 ` [PATCH 27/30] merge-recursive: Apply necessary modifications for directory renames Elijah Newren
2017-11-15 20:23 ` Stefan Beller
2017-11-16 3:54 ` Elijah Newren
2017-11-10 19:05 ` [PATCH 28/30] merge-recursive: Avoid clobbering untracked files with " Elijah Newren
2017-11-10 19:05 ` [RFC PATCH 29/30] merge-recursive: Fix overwriting dirty files involved in renames Elijah Newren
2017-11-10 19:05 ` [PATCH 30/30] merge-recursive: Fix remaining directory rename + dirty overwrite cases Elijah Newren
2017-11-10 22:27 ` [PATCH 00/30] Add directory rename detection to git Philip Oakley
2017-11-10 23:26 ` Elijah Newren
2017-11-13 15:04 ` Philip Oakley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGZ79kbmt7jt13D-HY90+LBaCHsqvDOYnrmJ41hR3YsgEceirg@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--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.
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).