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

Re: [PATCH] t3703: skip more tests using colons in file names on Windows

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jun 8, 2011, 06:22 UTC
Message-ID
<4DEF152C.5060005@viscovery.net>
In-Reply-To
<BANLkTik3K2GVZ5rzegYSXRrvROU_bzBdVw@mail.gmail.com>
Am 6/7/2011 15:43, schrieb Alex Riesen:
Show 8 quoted lines
> Use the same test and prerequisite as introduced in similar
> fix in 650af7ae8bdf92bd92df2.
> 
> Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
> ---
> 
> Why didn't Johannes noticed it, I wonder. The failing test was
> here all the time.
Good catch! Here's the explanation:
> -test_expect_success 'a file with the same (long) magic name exists' '
> -	: >":(icase)ha" &&

":foo" is the name of an alternate data stream on the current directory. Bash can successfully open and write such a "file". (But there is no way to list it, even though test -f detects its existence.)

> -	test_must_fail git add -n ":(icase)ha" &&

This 'git add' fails, either for the intended reason, or because regular directory listing functions do not detect the alternate data stream; I do not know.

> -	git add -n "./:(icase)ha"

This obviously succeeds because a regular open() call can open the alternate data stream just like any file.

Therefore, the test passes. This is on Windows XP with NTFS.
-- Hannes
Previous: Alex RiesenNext: Alex Riesen
Message 2 of 3 in “t3703: skip more tests using colons in file names on Windows”
  1. t3703: skip more tests using colons in file names on WindowsAlex Riesen, Jun 7, 2011
  2. Johannes SixtJun 8, 2011
  3. Alex RiesenJun 8, 2011

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.