2009-04-06 20:18:23 +00:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='git remote group handling'
|
2020-11-18 23:44:31 +00:00
|
|
|
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=main
|
tests: mark tests relying on the current default for `init.defaultBranch`
In addition to the manual adjustment to let the `linux-gcc` CI job run
the test suite with `master` and then with `main`, this patch makes sure
that GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME is set in all test scripts
that currently rely on the initial branch name being `master by default.
To determine which test scripts to mark up, the first step was to
force-set the default branch name to `master` in
- all test scripts that contain the keyword `master`,
- t4211, which expects `t/t4211/history.export` with a hard-coded ref to
initialize the default branch,
- t5560 because it sources `t/t556x_common` which uses `master`,
- t8002 and t8012 because both source `t/annotate-tests.sh` which also
uses `master`)
This trick was performed by this command:
$ sed -i '/^ *\. \.\/\(test-lib\|lib-\(bash\|cvs\|git-svn\)\|gitweb-lib\)\.sh$/i\
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master\
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME\
' $(git grep -l master t/t[0-9]*.sh) \
t/t4211*.sh t/t5560*.sh t/t8002*.sh t/t8012*.sh
After that, careful, manual inspection revealed that some of the test
scripts containing the needle `master` do not actually rely on a
specific default branch name: either they mention `master` only in a
comment, or they initialize that branch specificially, or they do not
actually refer to the current default branch. Therefore, the
aforementioned modification was undone in those test scripts thusly:
$ git checkout HEAD -- \
t/t0027-auto-crlf.sh t/t0060-path-utils.sh \
t/t1011-read-tree-sparse-checkout.sh \
t/t1305-config-include.sh t/t1309-early-config.sh \
t/t1402-check-ref-format.sh t/t1450-fsck.sh \
t/t2024-checkout-dwim.sh \
t/t2106-update-index-assume-unchanged.sh \
t/t3040-subprojects-basic.sh t/t3301-notes.sh \
t/t3308-notes-merge.sh t/t3423-rebase-reword.sh \
t/t3436-rebase-more-options.sh \
t/t4015-diff-whitespace.sh t/t4257-am-interactive.sh \
t/t5323-pack-redundant.sh t/t5401-update-hooks.sh \
t/t5511-refspec.sh t/t5526-fetch-submodules.sh \
t/t5529-push-errors.sh t/t5530-upload-pack-error.sh \
t/t5548-push-porcelain.sh \
t/t5552-skipping-fetch-negotiator.sh \
t/t5572-pull-submodule.sh t/t5608-clone-2gb.sh \
t/t5614-clone-submodules-shallow.sh \
t/t7508-status.sh t/t7606-merge-custom.sh \
t/t9302-fast-import-unpack-limit.sh
We excluded one set of test scripts in these commands, though: the range
of `git p4` tests. The reason? `git p4` stores the (foreign) remote
branch in the branch called `p4/master`, which is obviously not the
default branch. Manual analysis revealed that only five of these tests
actually require a specific default branch name to pass; They were
modified thusly:
$ sed -i '/^ *\. \.\/lib-git-p4\.sh$/i\
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master\
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME\
' t/t980[0167]*.sh t/t9811*.sh
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-11-18 23:44:19 +00:00
|
|
|
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME
|
|
|
|
|
2022-04-13 20:01:48 +00:00
|
|
|
TEST_PASSES_SANITIZE_LEAK=true
|
2009-04-06 20:18:23 +00:00
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
mark() {
|
|
|
|
echo "$1" >mark
|
|
|
|
}
|
|
|
|
|
|
|
|
update_repo() {
|
|
|
|
(cd $1 &&
|
|
|
|
echo content >>file &&
|
|
|
|
git add file &&
|
|
|
|
git commit -F ../mark)
|
|
|
|
}
|
|
|
|
|
|
|
|
update_repos() {
|
|
|
|
update_repo one $1 &&
|
|
|
|
update_repo two $1
|
|
|
|
}
|
|
|
|
|
|
|
|
repo_fetched() {
|
2015-12-23 13:45:54 +00:00
|
|
|
if test "$(git log -1 --pretty=format:%s $1 --)" = "$(cat mark)"; then
|
2009-04-06 20:18:23 +00:00
|
|
|
echo >&2 "repo was fetched: $1"
|
|
|
|
return 0
|
|
|
|
fi
|
|
|
|
echo >&2 "repo was not fetched: $1"
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
|
|
|
test_expect_success 'setup' '
|
|
|
|
mkdir one && (cd one && git init) &&
|
|
|
|
mkdir two && (cd two && git init) &&
|
2020-11-18 23:44:31 +00:00
|
|
|
git remote add -m main one one &&
|
|
|
|
git remote add -m main two two
|
2009-04-06 20:18:23 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'no group updates all' '
|
|
|
|
mark update-all &&
|
|
|
|
update_repos &&
|
|
|
|
git remote update &&
|
|
|
|
repo_fetched one &&
|
|
|
|
repo_fetched two
|
|
|
|
'
|
|
|
|
|
2011-06-16 13:42:48 +00:00
|
|
|
test_expect_success 'nonexistent group produces error' '
|
|
|
|
mark nonexistent &&
|
2009-04-06 20:18:23 +00:00
|
|
|
update_repos &&
|
2011-06-16 13:42:48 +00:00
|
|
|
test_must_fail git remote update nonexistent &&
|
2009-04-06 20:18:23 +00:00
|
|
|
! repo_fetched one &&
|
|
|
|
! repo_fetched two
|
|
|
|
'
|
|
|
|
|
2009-11-09 20:09:56 +00:00
|
|
|
test_expect_success 'updating group updates all members (remote update)' '
|
2009-04-06 20:18:23 +00:00
|
|
|
mark group-all &&
|
|
|
|
update_repos &&
|
|
|
|
git config --add remotes.all one &&
|
|
|
|
git config --add remotes.all two &&
|
|
|
|
git remote update all &&
|
|
|
|
repo_fetched one &&
|
|
|
|
repo_fetched two
|
|
|
|
'
|
|
|
|
|
2009-11-09 20:09:56 +00:00
|
|
|
test_expect_success 'updating group updates all members (fetch)' '
|
|
|
|
mark fetch-group-all &&
|
|
|
|
update_repos &&
|
|
|
|
git fetch all &&
|
|
|
|
repo_fetched one &&
|
|
|
|
repo_fetched two
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'updating group does not update non-members (remote update)' '
|
2009-04-06 20:18:23 +00:00
|
|
|
mark group-some &&
|
|
|
|
update_repos &&
|
|
|
|
git config --add remotes.some one &&
|
|
|
|
git remote update some &&
|
|
|
|
repo_fetched one &&
|
|
|
|
! repo_fetched two
|
|
|
|
'
|
|
|
|
|
2009-11-09 20:09:56 +00:00
|
|
|
test_expect_success 'updating group does not update non-members (fetch)' '
|
|
|
|
mark fetch-group-some &&
|
|
|
|
update_repos &&
|
|
|
|
git config --add remotes.some one &&
|
|
|
|
git remote update some &&
|
|
|
|
repo_fetched one &&
|
|
|
|
! repo_fetched two
|
|
|
|
'
|
|
|
|
|
2009-04-06 20:18:23 +00:00
|
|
|
test_expect_success 'updating remote name updates that remote' '
|
|
|
|
mark remote-name &&
|
|
|
|
update_repos &&
|
|
|
|
git remote update one &&
|
|
|
|
repo_fetched one &&
|
|
|
|
! repo_fetched two
|
|
|
|
'
|
|
|
|
|
|
|
|
test_done
|