"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.
-
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
