Tried Junio's latest suggestion. The resulting output and contents of the trash are attached as a tar.gz. Thanks for all your help guys, I'm sorry I can't contribute more but as I mentioned, I'm nowhere near proficient in c/c++ or the internals of Git. Paul On Jan 16, 2008 10:55 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > "Paul Umbers" <paul.umbers@xxxxxxxxx> writes: > > > OK, I think this worked (I'm a Java man, not C/C++). I downloaded the > > latest 1.5.3 source from the git repository and ran "make" with > > GIT_TEST_OPTS="--verbose --debug". Here's the output: > > > > paulumbers@Devteam29 ~/workspace/git/git-1.5.3/t > > $ make > > *** t0000-basic.sh *** > > * ok 1: .git/objects should be empty after git init in an empty repo. > > * ok 2: .git/objects should have 3 subdirectories. > > * ok 3: git update-index without --add should fail adding. > > * ok 4: git update-index with --add should succeed. > > * FAIL 5: writing tree out with git write-tree > > tree=$(git write-tree) > > Often the first error is the most interesting, as your build is > failing the most basic operation (like creating a tree), and > later parts of the test uses the tree to validate other aspects > of your build. > > After seeing the above error, running the test with -i (stop > immediately on failure): > > $ cd t > $ sh -x ./t0000-basic.sh -i -v > > and looking at the exact command that fails is the usual > approach for debugging something like this. During that > debugging session, the contents of the directory t/trash (which > is where the test script runs) left by the failed test is what > we often do. > > -- Computer Science is no more about computers than astronomy is about telescopes. --- Edsger W. Dijkstra Paul Umbers MSc MBCS MIAP paul.umbers@xxxxxxxxx
Attachment:
full_test_results.tar.gz
Description: GNU Zip compressed data
