d51b771dc0
The step to prepare a pre-rebase commit history is _identical_ in _all_ of the test cases (except of course the `setup` case). It should therefore clearly a part of the `setup` test case instead. As the `git filter-branch` command is quite costly on platforms where Unix shell scripting is simply slow (meaning: on Windows), this shaves off a noticeable part of the runtime: in this developer's setup, the time was reduced from ~1m25s to ~1m. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
135 lines
4.7 KiB
Bash
Executable File
135 lines
4.7 KiB
Bash
Executable File
#!/bin/sh
|
|
|
|
test_description='git rebase tests for -Xsubtree
|
|
|
|
This test runs git rebase and tests the subtree strategy.
|
|
'
|
|
. ./test-lib.sh
|
|
. "$TEST_DIRECTORY"/lib-rebase.sh
|
|
|
|
commit_message() {
|
|
git log --pretty=format:%s -1 "$1"
|
|
}
|
|
|
|
# There are a few bugs in the rebase with regards to the subtree strategy, and
|
|
# this test script tries to document them. First, the following commit history
|
|
# is generated (the onelines are shown, time flows from left to right):
|
|
#
|
|
# master1 - master2 - master3
|
|
# \
|
|
# README ---------------------- Add subproject master - master4 - files_subtree/master5
|
|
#
|
|
# Where the merge moves the files master[123].t into the subdirectory
|
|
# files_subtree/ and master4 as well as files_subtree/master5 add files to that
|
|
# directory directly.
|
|
#
|
|
# Then, in subsequent test cases, `git filter-branch` is used to distill just
|
|
# the commits that touch files_subtree/. To give it a final pre-rebase touch,
|
|
# an empty commit is added on top. The pre-rebase commit history looks like
|
|
# this:
|
|
#
|
|
# Add subproject master - master4 - files_subtree/master5 - Empty commit
|
|
#
|
|
# where the root commit adds three files: master1.t, master2.t and master3.t.
|
|
#
|
|
# This commit history is then rebased onto `master3` with the
|
|
# `-Xsubtree=files_subtree` option in three different ways:
|
|
#
|
|
# 1. using `--preserve-merges`
|
|
# 2. using `--preserve-merges` and --keep-empty
|
|
# 3. without specifying a rebase backend
|
|
|
|
test_expect_success 'setup' '
|
|
test_commit README &&
|
|
|
|
git init files &&
|
|
test_commit -C files master1 &&
|
|
test_commit -C files master2 &&
|
|
test_commit -C files master3 &&
|
|
|
|
: perform subtree merge into files_subtree/ &&
|
|
git fetch files refs/heads/master:refs/heads/files-master &&
|
|
git merge -s ours --no-commit --allow-unrelated-histories \
|
|
files-master &&
|
|
git read-tree --prefix=files_subtree -u files-master &&
|
|
git commit -m "Add subproject master" &&
|
|
|
|
: add two extra commits to rebase &&
|
|
test_commit -C files_subtree master4 &&
|
|
test_commit files_subtree/master5 &&
|
|
|
|
git checkout -b to-rebase &&
|
|
git filter-branch --prune-empty -f --subdirectory-filter files_subtree &&
|
|
git commit -m "Empty commit" --allow-empty
|
|
'
|
|
|
|
# FAILURE: Does not preserve master4.
|
|
test_expect_failure REBASE_P \
|
|
'Rebase -Xsubtree --preserve-merges --onto commit 4' '
|
|
reset_rebase &&
|
|
git checkout -b rebase-preserve-merges-4 to-rebase &&
|
|
git rebase -Xsubtree=files_subtree --preserve-merges --onto files-master master &&
|
|
verbose test "$(commit_message HEAD~)" = "files_subtree/master4"
|
|
'
|
|
|
|
# FAILURE: Does not preserve master5.
|
|
test_expect_failure REBASE_P \
|
|
'Rebase -Xsubtree --preserve-merges --onto commit 5' '
|
|
reset_rebase &&
|
|
git checkout -b rebase-preserve-merges-5 to-rebase &&
|
|
git rebase -Xsubtree=files_subtree --preserve-merges --onto files-master master &&
|
|
verbose test "$(commit_message HEAD)" = "files_subtree/master5"
|
|
'
|
|
|
|
# FAILURE: Does not preserve master4.
|
|
test_expect_failure REBASE_P \
|
|
'Rebase -Xsubtree --keep-empty --preserve-merges --onto commit 4' '
|
|
reset_rebase &&
|
|
git checkout -b rebase-keep-empty-4 to-rebase &&
|
|
git rebase -Xsubtree=files_subtree --keep-empty --preserve-merges --onto files-master master &&
|
|
verbose test "$(commit_message HEAD~2)" = "files_subtree/master4"
|
|
'
|
|
|
|
# FAILURE: Does not preserve master5.
|
|
test_expect_failure REBASE_P \
|
|
'Rebase -Xsubtree --keep-empty --preserve-merges --onto commit 5' '
|
|
reset_rebase &&
|
|
git checkout -b rebase-keep-empty-5 to-rebase &&
|
|
git rebase -Xsubtree=files_subtree --keep-empty --preserve-merges --onto files-master master &&
|
|
verbose test "$(commit_message HEAD~)" = "files_subtree/master5"
|
|
'
|
|
|
|
# FAILURE: Does not preserve Empty.
|
|
test_expect_failure REBASE_P \
|
|
'Rebase -Xsubtree --keep-empty --preserve-merges --onto empty commit' '
|
|
reset_rebase &&
|
|
git checkout -b rebase-keep-empty-empty to-rebase &&
|
|
git rebase -Xsubtree=files_subtree --keep-empty --preserve-merges --onto files-master master &&
|
|
verbose test "$(commit_message HEAD)" = "Empty commit"
|
|
'
|
|
|
|
# FAILURE: fatal: Could not parse object
|
|
test_expect_failure 'Rebase -Xsubtree --onto commit 4' '
|
|
reset_rebase &&
|
|
git checkout -b rebase-onto-4 to-rebase &&
|
|
git rebase -Xsubtree=files_subtree --onto files-master master &&
|
|
verbose test "$(commit_message HEAD~2)" = "files_subtree/master4"
|
|
'
|
|
|
|
# FAILURE: fatal: Could not parse object
|
|
test_expect_failure 'Rebase -Xsubtree --onto commit 5' '
|
|
reset_rebase &&
|
|
git checkout -b rebase-onto-5 to-rebase &&
|
|
git rebase -Xsubtree=files_subtree --onto files-master master &&
|
|
verbose test "$(commit_message HEAD~)" = "files_subtree/master5"
|
|
'
|
|
# FAILURE: fatal: Could not parse object
|
|
test_expect_failure 'Rebase -Xsubtree --onto empty commit' '
|
|
reset_rebase &&
|
|
git checkout -b rebase-onto-empty to-rebase &&
|
|
git rebase -Xsubtree=files_subtree --onto files-master master &&
|
|
verbose test "$(commit_message HEAD)" = "Empty commit"
|
|
'
|
|
|
|
test_done
|