Re: t3512 & t3513 'unexpected passes'

2017-11-21 Thread Junio C Hamano
Adam Dinwoodie writes: > I've seen the same unexpected passes, and had just completed the same > bisect run myself, although I fixed the build failure by cherry-picking > 82921316a ("SQUASH???", 2017-11-18) onto commits that wouldn't build, > given that commit seems to exist entirely to fix that

Re: t3512 & t3513 'unexpected passes'

2017-11-21 Thread Phillip Wood
On 21/11/17 10:44, Adam Dinwoodie wrote: > On Monday 20 November 2017 at 08:16 pm +, Ramsay Jones wrote: >> For several days, I have been staring at some 'unexpected passes' in >> the t3512-cherry-pick-submodule.sh and t3513-revert-submodule.sh test >> files (tests #11-13 in both cases). Thank

Re: t3512 & t3513 'unexpected passes'

2017-11-21 Thread Adam Dinwoodie
On Monday 20 November 2017 at 08:16 pm +, Ramsay Jones wrote: > For several days, I have been staring at some 'unexpected passes' in > the t3512-cherry-pick-submodule.sh and t3513-revert-submodule.sh test > files (tests #11-13 in both cases). > > I finally found time tonight to 'git bisect' th

t3512 & t3513 'unexpected passes'

2017-11-20 Thread Ramsay Jones
Hi Junio, For several days, I have been staring at some 'unexpected passes' in the t3512-cherry-pick-submodule.sh and t3513-revert-submodule.sh test files (tests #11-13 in both cases). I finally found time tonight to 'git bisect' the 'problem', and found that bisect fingered commit b5a812b298 ("s