From: Junio C Hamano <gitster@pobox.com>
To: "Paul Umbers" <paul.umbers@gmail.com>
Cc: "Alex Riesen" <raa.lkml@gmail.com>,
"Robin Rosenberg" <robin.rosenberg.lists@dewire.com>,
git@vger.kernel.org
Subject: Re: Git Cygwin - unable to create any repository - help!
Date: Wed, 16 Jan 2008 09:55:55 -0800 [thread overview]
Message-ID: <7v1w8hslhw.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <a5eb9c330801160742j645ee50p72ee0a93adf8f94f@mail.gmail.com> (Paul Umbers's message of "Wed, 16 Jan 2008 08:42:46 -0700")
"Paul Umbers" <paul.umbers@gmail.com> 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.
next prev parent reply other threads:[~2008-01-16 17:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 17:21 Git Cygwin - unable to create any repository - help! Paul Umbers
2008-01-14 20:29 ` Alex Riesen
2008-01-14 22:21 ` Paul Umbers
2008-01-15 5:48 ` Alex Riesen
2008-01-15 15:21 ` Paul Umbers
2008-01-15 20:04 ` Alex Riesen
2008-01-15 20:12 ` Paul Umbers
2008-01-15 21:20 ` Alex Riesen
2008-01-15 21:57 ` Paul Umbers
2008-01-15 22:51 ` Alex Riesen
2008-01-15 21:59 ` Paul Umbers
2008-01-15 22:55 ` Alex Riesen
2008-01-15 23:02 ` Robin Rosenberg
2008-01-16 7:18 ` Alex Riesen
2008-01-16 15:42 ` Paul Umbers
2008-01-16 17:55 ` Junio C Hamano [this message]
2008-01-16 18:10 ` Paul Umbers
2008-01-16 18:38 ` Alex Riesen
2008-01-16 18:57 ` Paul Umbers
2008-01-16 18:31 ` Alex Riesen
2008-01-16 18:48 ` Paul Umbers
2008-01-16 19:12 ` Alex Riesen
2008-01-16 19:17 ` Alex Riesen
2008-01-16 21:44 ` Paul Umbers
2008-01-16 23:45 ` Alex Riesen
2008-01-17 18:37 ` Paul Umbers
2008-01-17 18:51 ` Linus Torvalds
2008-01-17 19:17 ` Johannes Schindelin
2008-01-17 20:13 ` Paul Umbers
2008-01-17 20:24 ` Linus Torvalds
2008-01-17 20:38 ` Pascal Obry
2008-01-17 20:50 ` Johannes Schindelin
2008-01-17 20:53 ` Pascal Obry
2008-01-17 22:32 ` Paul Umbers
2008-01-17 20:18 ` Alex Riesen
2008-01-17 18:53 ` Nicholas Wourms
2008-01-17 20:30 ` Alex Riesen
2008-01-16 18:50 ` Paul Umbers
2008-01-15 17:08 ` Pascal Obry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v1w8hslhw.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=paul.umbers@gmail.com \
--cc=raa.lkml@gmail.com \
--cc=robin.rosenberg.lists@dewire.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).