v1.7.3-rc2 has t7003 breakage on Mac OS X 10.6.4

Hi,

Just noticed a new test failure in t7003 on Mac OS X 10.6.4. Wasn't present in rc1, but is in rc2.

Relevant section of "make test" output:

  https://wincent.com/snippets/7

The failing test is "30 automatic remapping to ancestor with filename filters".

Here's a segment of the output of "sh -x t7003-filter-branch.sh" from inside the "t" directory (this is just the part near test 30):

  https://wincent.com/snippets/5

And here's the entire output of "sh -x t7003-filter-branch.sh" (thousands of lines long):

  https://wincent.com/snippets/6

This is on a pretty "stock" version of Mac OS X, using Apple-supplied Bash:

  GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0)
  Copyright (C) 2007 Free Software Foundation, Inc.

According to "git bisect", this is the change that is responsible for the breakage:

7ec344d802970782036146e29ba2213e86d49fe1 is the first bad commit
commit 7ec344d802970782036146e29ba2213e86d49fe1
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Aug 27 20:44:56 2010 +0000

    filter-branch: retire --remap-to-ancestor
    
    We can be clever and know by ourselves when we need the behavior
    implied by "--remap-to-ancestor". No need to encumber users by having
    them exposed to it as a tunable. (Option kept for backward compatibility,
    but it's now a no-op.)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>

:040000 040000 d67e263477f73a8f14528e6e7a6a84506c8febf4 3d6f1b24dc76f44e0cdb28b5d2738b46cb339f32 M Documentation :100755 100755 88fb0f070e5f32c62ae47f90f1f27ffeef836d8f 962a93b586571eb6fc60aae53c77f6e6b9fb281f M git-filter-branch.sh :040000 040000 e43459803e2662799c23a81fbe2f47abe2f9b0f9 afc5fd99e7c1ffd56adcb0dedba634463f686cc0 M t

Please let me know if you need any further info to troubleshoot the issue.

Cheers, Wincent

Am 9/16/2010 9:18, schrieb Wincent Colaiuta:

git pull git://github.com/gitster/git.git bg/fix-t7003

-- Hannes

El 16/09/2010, a las 11:04, Johannes Sixt escribió:

Ok, just tested it and confirmed that that topic fixes the test breakage for me, thanks to 77f2e4f5f.

Curses on the Mac's case-insensitive filesystem, again...

Cheers, Wincent

Johannes Sixt <j.sixt@viscovery.net> writes:

Thanks.