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

Re: [PATCH 4/5] Test and fix normalize_path_copy()

From
René Scharfe <rene.scharfe@lsrfire.ath.cx>
Date
Feb 8, 2009, 14:46 UTC
Message-ID
<498EF028.3040702@lsrfire.ath.cx>
In-Reply-To
<1234019311-6449-5-git-send-email-j6t@kdbg.org>
Johannes Sixt schrieb:
> Moreover, the test case descriptions of t0060 now include the test data and
> expected outcome.

The test still fails in a lot of cases for me, because "/" is translated to the installation path of msys. E.g. with the patch at the end, which shows the results in addition to input and expected output, I get several cases like this (the first test call checks the return code):

* FAIL 2: normalize absolute: '/' => '/'
	test 0 = 0 && test 'C:/Program Files (x86)/msysgit/msysgit' = '/'
* FAIL 32: longest ancestor: '/foo' '/' => '0'
	test 0 = 0 && test '38' = '0'

I'm not sure what to do about it. Should test-path-utils translate it back into "root is / is root"? Should the test script look up "/" at the top and just append this value to all paths? Unpretty.

And then there's this:
* FAIL 7: normalize absolute: '/./..' => '++failed++'
	test 0 = 0 && test 'C:/Program Files (x86)/msysgit/msysgit' = '++failed++'
*   ok 8: normalize absolute: '/../.' => '++failed++'

A printf() added to the top of normalize_path_copy() tells me that you can add as many "/.." as you want after a path starting with "/.", it will always translate into the install directory of msys regardless.

Anyway, here's the patch mentioned above:
diff --git a/t/t0060-path-utils.sh b/t/t0060-path-utils.sh
index 4ed1f0b..d5a38a6 100755
--- a/t/t0060-path-utils.sh
+++ b/t/t0060-path-utils.sh
@@ -8,13 +8,17 @@ test_description='Test various path utilities'
 . ./test-lib.sh
 
 norm_abs() {
-	test_expect_success "normalize absolute: $1 => $2" \
-	"test \"\$(test-path-utils normalize_path_copy '$1')\" = '$2'"
+	result=$(test-path-utils normalize_path_copy "$1")
+	rc=$?
+	test_expect_success "normalize absolute: '$1' => '$2'" \
+	"test $rc = 0 && test '$result' = '$2'"
 }
 
 ancestor() {
-	test_expect_success "longest ancestor: $1 $2 => $3" \
-	"test \"\$(test-path-utils longest_ancestor_length '$1' '$2')\" = '$3'"
+	result=$(test-path-utils longest_ancestor_length "$1" "$2")
+	rc=$?
+	test_expect_success "longest ancestor: '$1' '$2' => '$3'" \
+	"test $rc = 0 && test '$result' = '$3'"
 }
 
 norm_abs "" ""
Previous: Johannes SixtNext: Johannes Sixt
Message 24 of 26 in “fix crash in path.c on Windows”
  1. fix crash in path.c on WindowsRené Scharfe, Feb 4, 2009
  2. Junio C HamanoFeb 4, 2009
  3. Johannes SixtFeb 5, 2009
  4. René ScharfeFeb 5, 2009
  5. Johannes SixtFeb 5, 2009
  6. Robin RosenbergFeb 5, 2009
  7. fix t1504 on WindowsRené Scharfe, Feb 5, 2009
  8. Johannes SixtFeb 6, 2009
  9. Johannes SchindelinFeb 6, 2009
  10. Johannes SixtFeb 6, 2009
  11. Johannes SchindelinFeb 6, 2009
  12. Johannes SixtFeb 6, 2009
  13. René ScharfeFeb 6, 2009
  14. Johannes SixtFeb 6, 2009
  15. René ScharfeFeb 6, 2009
  16. 0/5 Consolidate path normalization functionsJohannes Sixt, Feb 7, 2009
  17. 1/5 Make test-path-utils more robust against incorrect useJohannes Sixt, Feb 7, 2009
  18. 2/5 Move sanitary_path_copy() to path.c and rename it to normalize_path_copy()Johannes Sixt, Feb 7, 2009
  19. 3/5 Fix GIT_CEILING_DIRECTORIES on WindowsJohannes Sixt, Feb 7, 2009
  20. 4/5 Test and fix normalize_path_copy()Johannes Sixt, Feb 7, 2009
  21. 5/5 Remove unused normalize_absolute_path()Johannes Sixt, Feb 7, 2009
  22. Robin RosenbergFeb 8, 2009
  23. Johannes SixtFeb 8, 2009
  24. René ScharfeFeb 8, 2009
  25. Johannes SixtFeb 8, 2009
  26. René ScharfeFeb 7, 2009

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.