On Fri, Jul 20, 2007 at 10:12:42AM +0100, Sam Morris wrote: > Indeed, my build now fails at a different point: > > *** t9200-git-cvsexportcommit.sh *** > * ok 1: New file > * ok 2: Remove two files, add two and update two > * ok 3: Fail to change binary more than one generation old > * ok 4: Remove only binary files > * ok 5: Remove only a text file > * ok 6: New file with spaces in file name > * FAIL 7: Update file with spaces in file name > echo Ok then >>"G g/with spaces.txt" && > cat ../test9200a.png >>"G g/with spaces.png" && \ > git add "G g/with spaces.png" && > git commit -a -m "Update with spaces" && > id=$(git rev-list --max-count=1 HEAD) && > (cd "$CVSWORK" && > git-cvsexportcommit -c $id > test "$(echo $(sort "G g/CVS/Entries"|cut -d/ > -f2,3,5))" = "with spaces.png/1.2/-kb with spaces.txt/1.2/" > ) > * ok 8: File with non-ascii file name > * ok 9: Mismatching patch should fail > * ok 10: Retain execute bit > * failed 1 among 10 test(s) > > Any ideas?
You can set 'GIT_TEST_OPTS=--verbose --debug' while building (see t/Makefile), this should give you more details such as the stderr output of the failed test. Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
