Le mardi 20 novembre 2007, carbonated beverage a écrit : [...] > I tried running the test manually and noticed something weird as well: > > ramune/lycaeum:t: sh t9106-git-svn-dcommit-clobber-series.sh > * ok 1: initialize repo > * ok 2: (supposedly) non-conflicting change from SVN > * ok 3: some unrelated changes to git > * ok 4: change file but in unrelated area > * passed all 4 test(s) > ramune/lycaeum:t: > ramune/lycaeum:t: pwd > /home/ramune/src/git/git/t > ramune/lycaeum:t: > ramune/lycaeum:t: sh t9106-git-svn-dcommit-clobber-series.sh > * ok 1: initialize repo > * ok 2: (supposedly) non-conflicting change from SVN > * ok 3: some unrelated changes to git > * FAIL 4: change file but in unrelated area > > test x"`sed -n -e 4p < file`" = x4 && > test x"`sed -n -e 7p < file`" = x7 && > perl -i -p -e 's/^4$/4444/' file && > perl -i -p -e 's/^7$/7777/' file && > test x"`sed -n -e 4p < file`" = x4444 && > test x"`sed -n -e 7p < file`" = x7777 && > git commit -m '4 => 4444, 7 => 7777' file && > git svn dcommit && > svn up tmp && > cd tmp && > test x"`sed -n -e 4p < file`" = x4444 && > test x"`sed -n -e 7p < file`" = x7777 && > test x"`sed -n -e 58p < file`" = x5588 && > test x"`sed -n -e 61p < file`" = x6611 > > * failed 1 among 4 test(s) > > So it succeeds once, then fails. > > /bin/sh is dash 0.5.3-7 from Debian. > > Any additional information needed? Could you try running the test twice when you bisect ? This way bisecting should give you the real first bad commit. Could you also try to find the line that fails in the 4th test ? For example you could replace all the trailing "&&" in this test with a new line that contains "echo $?". Thanks in advance, Christian. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
