sparse-checkout test failures [powerpc-darwin8]

Hi,
 	With git 1.7.9.4, I'm seeing test failures with
t1011-read-tree-sparse-checkout.sh.

not ok - 16 read-tree adds to worktree, dirty case # # echo init.t >.git/info/sparse-checkout && # git checkout -f removed && # mkdir sub && # echo dirty >sub/added && # read_tree_u_must_succeed -u -m HEAD^ && # grep -q dirty sub/added # not ok - 17 index removal and worktree narrowing at the same time # # >empty && # echo init.t >.git/info/sparse-checkout && # echo sub/added >>.git/info/sparse-checkout && # git checkout -f top && # echo init.t >.git/info/sparse-checkout && # git checkout removed && # git ls-files sub/added >result && # test ! -f sub/added && # test_cmp empty result # not ok - 18 read-tree --reset removes outside worktree # # >empty && # echo init.t >.git/info/sparse-checkout && # git checkout -f top && # git reset --hard removed && # git ls-files sub/added >result && # test_cmp empty result # not ok - 19 print errors when failed to update worktree # # echo sub >.git/info/sparse-checkout && # git checkout -f init && # mkdir sub && # touch sub/added sub/addedtoo && # test_must_fail git checkout top 2>actual && # cat >expected <<\EOF && # error: The following untracked working tree files would be overwritten b y checkout: # sub/added # sub/addedtoo # Please move or remove them before you can switch branches. # Aborting # EOF # test_cmp expected actual # # failed 5 among 19 test(s) 1..19 make[2]: *** [t1011-read-tree-sparse-checkout.sh] Error 1

not ok - 16 not just commits # # echo replaced >file && # git add file && # REPLACED=$(git rev-parse :file) && # mv file file.replaced && # # echo original >file && # git add file && # ORIGINAL=$(git rev-parse :file) && # git update-ref refs/replace/$ORIGINAL $REPLACED && # mv file file.original && # # git checkout file && # test_cmp file.replaced file # # failed 1 among 16 test(s) 1..16 make[2]: *** [t6050-replace.sh] Error 1

Everything else that's "not ok" is a known breakage.

[from http://paste.lisp.org/display/128628]

Any idea what's going wrong? Anyone else seeing these failures?

Fang