From: Thomas Gummerer <t.gummerer@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH tg/add-chmod+x-fix 1/2] t3700-add: create subdirectory gently
Date: Tue, 20 Sep 2016 20:28:28 +0100 [thread overview]
Message-ID: <20160920192828.GF8254@hank> (raw)
In-Reply-To: <cee3c784-8f03-c524-2f67-d35cb3755a41@kdbg.org>
Hi Johannes,
On 09/20, Johannes Sixt wrote:
> The subdirectory 'sub' is created early in the test file. Later, a test
> case removes it during its clean-up actions. However, this test case is
> protected by POSIXPERM. Consequently, 'sub' remains when the POSIXPERM
> prerequisite is not satisfied. Later, a recently introduced test case
> creates 'sub' again. Use -p with mkdir so that it does not fail if 'sub'
> already exists.
Thanks for catching and fixing this. Having a look at the tests shows
that this happens through a git reset --hard at the start of the tests
that require POSIXPERM, which makes me wonder whether we should do
such a cleanup somewhere unconditionally, or move the tests that do
require POSIXPERM to the end of the test file to possibly prevent
similar breakages in the future?
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
> ---
> t/t3700-add.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/t/t3700-add.sh b/t/t3700-add.sh
> index 0a962a6..16ab2da 100755
> --- a/t/t3700-add.sh
> +++ b/t/t3700-add.sh
> @@ -380,7 +380,7 @@ test_expect_success 'no file status change if no pathspec is given' '
> '
>
> test_expect_success 'no file status change if no pathspec is given in subdir' '
> - mkdir sub &&
> + mkdir -p sub &&
> (
> cd sub &&
> >sub-foo1 &&
> --
> 2.10.0.85.gea34e30
>
--
Thomas
prev parent reply other threads:[~2016-09-20 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 6:16 [PATCH tg/add-chmod+x-fix 1/2] t3700-add: create subdirectory gently Johannes Sixt
2016-09-20 6:18 ` [PATCH tg/add-chmod+x-fix 2/2] t3700-add: protect one --chmod=+x test with POSIXPERM Johannes Sixt
2016-09-20 19:34 ` Thomas Gummerer
2016-09-21 18:12 ` Junio C Hamano
2016-09-21 20:47 ` Johannes Sixt
2016-09-21 20:47 ` Junio C Hamano
2016-09-21 20:58 ` Johannes Sixt
2016-09-21 21:12 ` Junio C Hamano
2016-09-22 5:06 ` Johannes Sixt
2016-09-22 21:01 ` Thomas Gummerer
2016-09-20 19:28 ` Thomas Gummerer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160920192828.GF8254@hank \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.