git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] t3700: fix broken test under !POSIXPERM

From
Ramsay Jones <ramsay@ramsayjones.plus.com>
Date
Aug 8, 2017, 19:32 UTC
Message-ID
<d6c6c246-ef15-64dd-208f-e8a4c240bd3d@ramsayjones.plus.com>
In-Reply-To
<7c104440-5903-472c-36c2-779cd0e81be5@web.de>
On 08/08/17 20:21, René Scharfe wrote:
Show 6 quoted lines
> 76e368c378 (t3700: fix broken test under !SANITY) explains that the test
> 'git add --chmod=[+-]x changes index with already added file' can fail
> if xfoo3 is still present as a symlink from a previous test and deletes
> it with rm(1).  That still leaves it present in the index, which causes
> the test to fail if POSIXPERM is not defined.  Get rid of it by calling
> "git reset --hard" as well, as 76e368c378 already mentioned in passing.

Hmm, I don't think its POSIXPERM (which is defined on cygwin) but the lack of SANITY that is the problem. The test would fail on Linux as well, if it skipped the prior tests marked with SANITY (they get rid of the xfoo3->xfoo2 symlinks, among others).

Ack, this fixes it for me.

ATB, Ramsay Jones

Show 22 quoted lines
> 
> Helped-by: Adam Dinwoodie <adam@dinwoodie.org>
> Signed-off-by: Rene Scharfe <l.s.r@web.de>
> ---
> Change since v1: Keep the rm(1) call to avoid a problem on Cygwin.
> 
>  t/t3700-add.sh | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/t/t3700-add.sh b/t/t3700-add.sh
> index f3a4b4a913..0aae21d698 100755
> --- a/t/t3700-add.sh
> +++ b/t/t3700-add.sh
> @@ -356,6 +356,7 @@ test_expect_success POSIXPERM,SYMLINKS 'git add --chmod=+x with symlinks' '
>  
>  test_expect_success 'git add --chmod=[+-]x changes index with already added file' '
>  	rm -f foo3 xfoo3 &&
> +	git reset --hard &&
>  	echo foo >foo3 &&
>  	git add foo3 &&
>  	git add --chmod=+x foo3 &&
> 
Previous: René ScharfeNext: Ramsay Jones
Message 3 of 4 in “t3700: fix broken test under !POSIXPERM”
  1. t3700: fix broken test under !POSIXPERMRené Scharfe, Aug 7, 2017
  2. t3700: fix broken test under !POSIXPERMRené Scharfe, Aug 8, 2017
  3. Ramsay JonesAug 8, 2017
  4. Ramsay JonesAug 8, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.