Message ID | 20231003185047.2697995-3-heftig@archlinux.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [1/6] submodule--helper: use submodule_from_path in set-{url,branch} | expand |
"Jan Alexander Steffens (heftig)" <heftig@archlinux.org> writes: > Subject: Re: [PATCH 3/6] t7419: Actually test the branch switching "Actually" -> "actually". > The submodule repo the test set up had the 'topic' branch checked out, > meaning the repo's default branch (HEAD) is the 'topic' branch. > > The following tests then pretended to switch between the default branch > and the 'topic' branch. This was papered over by continually adding > commits to the 'topic' branch and checking if the submodule gets updated > to this new commit. > > Return the submodule repo to the 'main' branch after setup so we can > actually test the switching behavior. Nicely spotted. > diff --git a/t/t7419-submodule-set-branch.sh b/t/t7419-submodule-set-branch.sh > index 232065504c..5ac16d0eb7 100755 > --- a/t/t7419-submodule-set-branch.sh > +++ b/t/t7419-submodule-set-branch.sh > @@ -11,23 +11,28 @@ as expected. > > TEST_PASSES_SANITIZE_LEAK=true > TEST_NO_CREATE_REPO=1 > + > +GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=main > +export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME And it is good that this variable is used to prepare the test for both kinds of CI runs that use 'main' or 'master' as the default branch.
diff --git a/t/t7419-submodule-set-branch.sh b/t/t7419-submodule-set-branch.sh index 232065504c..5ac16d0eb7 100755 --- a/t/t7419-submodule-set-branch.sh +++ b/t/t7419-submodule-set-branch.sh @@ -11,23 +11,28 @@ as expected. TEST_PASSES_SANITIZE_LEAK=true TEST_NO_CREATE_REPO=1 + +GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=main +export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME + . ./test-lib.sh test_expect_success 'setup' ' git config --global protocol.file.allow always ' test_expect_success 'submodule config cache setup' ' mkdir submodule && (cd submodule && git init && echo a >a && git add . && git commit -ma && git checkout -b topic && echo b >a && git add . && - git commit -mb + git commit -mb && + git checkout main ) && mkdir super && (cd super && @@ -57,41 +62,38 @@ test_expect_success 'test submodule set-branch --branch' ' ' test_expect_success 'test submodule set-branch --default' ' - test_commit -C submodule c && (cd super && git submodule set-branch --default submodule && ! grep branch .gitmodules && git submodule update --remote && cat <<-\EOF >expect && - c + a EOF git -C submodule show -s --pretty=%s >actual && test_cmp expect actual ) ' test_expect_success 'test submodule set-branch -b' ' - test_commit -C submodule b && (cd super && git submodule set-branch -b topic submodule && grep "branch = topic" .gitmodules && git submodule update --remote && cat <<-\EOF >expect && b EOF git -C submodule show -s --pretty=%s >actual && test_cmp expect actual ) ' test_expect_success 'test submodule set-branch -d' ' - test_commit -C submodule d && (cd super && git submodule set-branch -d submodule && ! grep branch .gitmodules && git submodule update --remote && cat <<-\EOF >expect && - d + a EOF git -C submodule show -s --pretty=%s >actual && test_cmp expect actual
The submodule repo the test set up had the 'topic' branch checked out, meaning the repo's default branch (HEAD) is the 'topic' branch. The following tests then pretended to switch between the default branch and the 'topic' branch. This was papered over by continually adding commits to the 'topic' branch and checking if the submodule gets updated to this new commit. Return the submodule repo to the 'main' branch after setup so we can actually test the switching behavior. Signed-off-by: Jan Alexander Steffens (heftig) <heftig@archlinux.org> --- t/t7419-submodule-set-branch.sh | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-)