threads / discuss / 30149

sparse-checkout test failures [powerpc-darwin8]

Subject: sparse-checkout test failures [powerpc-darwin8]

## tl;dr

4 messages between Apr 4, 2012 and Apr 5, 2012.

replies: 3people: 3as markdown or json

David Fang· Apr 4, 2012, 20:20 UTC · lore
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
-- 
David Fang
http://www.csl.cornell.edu/~fang/
Junio C Hamano· Apr 4, 2012, 21:34 UTC · re: David Fang · lore

Re: sparse-checkout test failures [powerpc-darwin8]

David Fang <fang@csl.cornell.edu> writes:
> 	With git 1.7.9.4, I'm seeing test failures with
> t1011-read-tree-sparse-checkout.sh.

Hrm. Do you mean 1.7.9 worked and 1.7.9.4 doesn't, or you just happened to try 1.7.9.4 and do not know if this is a regression?

I do not have any Darwin or PowerPC boxes, but the answer to the above may help others who do to help diagnosing the issue further.

Thanks.
David Fang· Apr 4, 2012, 21:41 UTC · re: Junio C Hamano · lore

Re: sparse-checkout test failures [powerpc-darwin8]

Show 8 quoted lines
> David Fang <fang@csl.cornell.edu> writes:
>> 	With git 1.7.9.4, I'm seeing test failures with
>> t1011-read-tree-sparse-checkout.sh.
>
> Hrm.  Do you mean 1.7.9 worked and 1.7.9.4 doesn't, or you just happened
> to try 1.7.9.4 and do not know if this is a regression?
> I do not have any Darwin or PowerPC boxes, but the answer to the above may
> help others who do to help diagnosing the issue further.

Unfortunately, I didn't try any of the earlier 1.7.9.x releases, the previous one I tested was 1.7.8.4, which passed all tests (except for known breakages, and a few other disabled tests).

-- 
David Fang
http://www.csl.cornell.edu/~fang/
Nguyen Thai Ngoc Duy· Apr 5, 2012, 05:35 UTC · re: David Fang · lore

Re: sparse-checkout test failures [powerpc-darwin8]

On Thu, Apr 5, 2012 at 4:41 AM, David Fang <fang@csl.cornell.edu> wrote:
Show 15 quoted lines
>> David Fang <fang@csl.cornell.edu> writes:
>>>
>>>        With git 1.7.9.4, I'm seeing test failures with
>>> t1011-read-tree-sparse-checkout.sh.
>>
>>
>> Hrm.  Do you mean 1.7.9 worked and 1.7.9.4 doesn't, or you just happened
>> to try 1.7.9.4 and do not know if this is a regression?
>> I do not have any Darwin or PowerPC boxes, but the answer to the above may
>> help others who do to help diagnosing the issue further.
>
>
> Unfortunately, I didn't try any of the earlier 1.7.9.x releases, the
> previous one I tested was 1.7.8.4, which passed all tests (except for known
> breakages, and a few other disabled tests).

Please try to bisect if you have time, or at least v1.7.9, and run those two tests with "-v".

-- 
Duy

← back to recent threads