From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH 1/2] t4151: document a pair of am --abort bugs
Date: Wed, 8 Sep 2021 12:13:11 +0700 [thread overview]
Message-ID: <96e001e5-56d7-7806-19ad-ac41f833b0a7@gmail.com> (raw)
In-Reply-To: <b8a418bc63ab0a4add25724a11eb5f992e3d4472.1631067429.git.gitgitgadget@gmail.com>
On 08/09/21 09.17, Elijah Newren via GitGitGadget wrote:
> From: Elijah Newren <newren@gmail.com>
>
> Signed-off-by: Elijah Newren <newren@gmail.com>
> ---
> t/t4151-am-abort.sh | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/t/t4151-am-abort.sh b/t/t4151-am-abort.sh
> index 9d8d3c72e7e..501a7a9d211 100755
> --- a/t/t4151-am-abort.sh
> +++ b/t/t4151-am-abort.sh
> @@ -23,7 +23,11 @@ test_expect_success setup '
> test_tick &&
> git commit -a -m $i || return 1
> done &&
> + git branch changes &&
> git format-patch --no-numbered initial &&
> + git checkout -b conflicting initial &&
> + echo different >>file-1 &&
> + git commit -a -m different &&
> git checkout -b side initial &&
> echo local change >file-2-expect
> '
> @@ -191,4 +195,31 @@ test_expect_success 'am --abort leaves index stat info alone' '
> git diff-files --exit-code --quiet
> '
>
> +test_expect_failure 'git am --abort return failed exit status when it fails' '
> + test_when_finished "rm -rf file-2/ && git reset --hard" &&
> + git checkout changes &&
> + git format-patch -1 --stdout conflicting >changes.mbox &&
> + test_must_fail git am --3way changes.mbox &&
> +
> + git rm file-2 &&
> + mkdir file-2 &&
> + echo precious >file-2/somefile &&
> + test_must_fail git am --abort &&
> + test_path_is_dir file-2/
> +'
> +
> +test_expect_failure 'git am --abort returns us to a clean state' '
> + git checkout changes &&
> + git format-patch -1 --stdout conflicting >changes.mbox &&
> + test_must_fail git am --3way changes.mbox &&
> +
> + # Make a change related to the rest of the am work
> + echo related change >>file-2 &&
> +
> + # Abort, and expect the related change to go away too
> + git am --abort &&
> + git status --porcelain -uno >actual &&
> + test_must_be_empty actual
> +'
> +
> test_done
>
I expect BUGS section in git-am(1) to be added to describe known bugs
you demonstrated above, judging from the patch subject.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-09-08 5:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 2:17 [PATCH 0/2] A pair of git am --abort issues Elijah Newren via GitGitGadget
2021-09-08 2:17 ` [PATCH 1/2] t4151: document a pair of am --abort bugs Elijah Newren via GitGitGadget
2021-09-08 5:13 ` Bagas Sanjaya [this message]
2021-09-08 5:24 ` Elijah Newren
2021-09-08 7:02 ` Junio C Hamano
2021-09-08 8:00 ` Elijah Newren
2021-09-08 16:33 ` Junio C Hamano
2021-09-08 2:17 ` [PATCH 2/2] am: fix incorrect exit status on am fail to abort Elijah Newren via GitGitGadget
2021-09-08 16:33 ` Junio C Hamano
2021-09-08 8:08 ` [PATCH 0/2] A pair of git am --abort issues Johannes Schindelin
2021-09-10 10:31 ` [PATCH v2 0/3] " Elijah Newren via GitGitGadget
2021-09-10 10:31 ` [PATCH v2 1/3] git-am.txt: clarify --abort behavior Elijah Newren via GitGitGadget
2021-09-10 10:31 ` [PATCH v2 2/3] t4151: add a few am --abort tests Elijah Newren via GitGitGadget
2021-09-10 10:31 ` [PATCH v2 3/3] am: fix incorrect exit status on am fail to abort Elijah Newren via GitGitGadget
2021-09-13 12:08 ` [PATCH v2 0/3] A pair of git am --abort issues Johannes Schindelin
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=96e001e5-56d7-7806-19ad-ac41f833b0a7@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.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).