From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
git@vger.kernel.org, Andreas Schwab <schwab@suse.de>
Subject: Re: [PATCH v2] t6026: ensure that long-running script really is
Date: Fri, 11 Nov 2016 22:15:32 +0100 [thread overview]
Message-ID: <c4cdd21e-0cef-8255-75f2-90c84f271e02@kdbg.org> (raw)
In-Reply-To: <xmqqmvh5207k.fsf@gitster.mtv.corp.google.com>
Am 11.11.2016 um 22:09 schrieb Junio C Hamano:
> Johannes Sixt <j6t@kdbg.org> writes:
>
>> Am 11.11.2016 um 21:48 schrieb Junio C Hamano:
>>> Johannes Sixt <j6t@kdbg.org> writes:
>>>
>>>> Good point. Here is an updated version.
>>>
>>> Unfortunately, I already took the version before this one and
>>> started my integration cycle today. I'll wiggle this in; it
>>> essentially is about adding a big comment to explain what is going
>>> on and then moving the when-finished down below it, right?
>>
>> Correct.
>
> Thanks. It has become like so:
>
> -- >8 --
> From: Johannes Sixt <j6t@kdbg.org>
> Date: Fri, 11 Nov 2016 21:24:44 +0100
> Subject: [PATCH] t6026: clarify the point of "kill $(cat sleep.pid)"
>
> We lengthened the time the leftover process sleeps in the previous
> commit to make sure it will be there while 'git merge' runs and
> finishes. It therefore needs to be killed before leaving the test.
> And it needs to be killed even when 'git merge' fails, so it has to
> be triggered via test_when_finished mechanism.
>
> Explain all that in a large comment, and move the use site of
> test_when_finished to immediately before 'git merge' invocation,
> where the process is spawned.
>
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Perfect, thank you very much.
> ---
> t/t6026-merge-attr.sh | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/t/t6026-merge-attr.sh b/t/t6026-merge-attr.sh
> index 348d78b205..8f9b48a493 100755
> --- a/t/t6026-merge-attr.sh
> +++ b/t/t6026-merge-attr.sh
> @@ -187,12 +187,20 @@ test_expect_success 'custom merge does not lock index' '
> sleep 3600 &
> echo $! >sleep.pid
> EOF
> - test_when_finished "kill \$(cat sleep.pid)" &&
>
> test_write_lines >.gitattributes \
> "* merge=ours" "text merge=sleep-an-hour" &&
> test_config merge.ours.driver true &&
> test_config merge.sleep-an-hour.driver ./sleep-an-hour.sh &&
> +
> + # We are testing that the custom merge driver does not block
> + # index.lock on Windows due to an inherited file handle.
> + # To ensure that the backgrounded process ran sufficiently
> + # long (and has been started in the first place), we do not
> + # ignore the result of the kill command.
> + # By packaging the command in test_when_finished, we get both
> + # the correctness check and the clean-up.
> + test_when_finished "kill \$(cat sleep.pid)" &&
> git merge master
> '
>
>
prev parent reply other threads:[~2016-11-11 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 13:51 [PATCH] t6026: ensure that long-running script really is Johannes Schindelin
2016-11-10 23:53 ` Junio C Hamano
2016-11-11 6:50 ` Johannes Sixt
2016-11-11 8:41 ` Jeff King
2016-11-11 20:24 ` [PATCH v2] " Johannes Sixt
2016-11-11 20:48 ` Junio C Hamano
2016-11-11 20:54 ` Johannes Sixt
2016-11-11 21:09 ` Junio C Hamano
2016-11-11 21:15 ` Johannes Sixt [this message]
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=c4cdd21e-0cef-8255-75f2-90c84f271e02@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=peff@peff.net \
--cc=schwab@suse.de \
/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).