From: "Tim O'Callaghan" <timo@dspsrv.com>
To: git@vger.kernel.org
Subject: Problem with Git in Cygwin on x86-64 platform
Date: Sat, 22 Apr 2006 04:30:30 +0200 [thread overview]
Message-ID: <20060422023029.GC2444@Zangband> (raw)
When running a 'make test' under cygwin on my 64bit machine, and got
the output below. The reason i cite the 64bit cygwin platform being a
difference is that i have run 'make test' on the exact same codebase
on a 32 bit machine. The only difference in compile environment is
that the cygwin install on the 64 bit machine is as of today, and the
32 bit machine was about three days ago.
----
*** t0000-basic.sh ***
* ok 1: .git/objects should be empty after git-init-db 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.
* ok 5: writing tree out with git-write-tree
* ok 6: validate object ID of a known tree.
* ok 7: git-update-index without --remove should fail removing.
* FAIL 8: git-update-index with --remove should be able to remove.
git-update-index --remove should-be-empty
* ok 9: git-write-tree should be able to write an empty tree.
* FAIL 10: validate object ID of a known tree.
test "$tree" = 4b825dc642cb6eb9a060e54bf8d69288fbee4904
* FAIL 11: adding various types of objects with git-update-index --add.
find path* ! -type d -print | xargs git-update-index --add
* ok 12: showing stage with git-ls-files --stage
* FAIL 13: validate git-ls-files output for a known tree.
diff current expected
* ok 14: writing tree out with git-write-tree.
* FAIL 15: validate object ID for a known tree.
test "$tree" = 087704a96baf1c2d1c869a8b084481e121c88b5b
* ok 16: showing tree with git-ls-tree
* FAIL 17: git-ls-tree output for a known tree.
diff current expected
* ok 18: showing tree with git-ls-tree -r
* FAIL 19: git-ls-tree -r output for a known tree.
diff current expected
* FAIL 20: git-read-tree followed by write-tree should be idempotent.
git-read-tree $tree &&
test -f .git/index &&
newtree=$(git-write-tree) &&
test "$newtree" = "$tree"
* FAIL 21: validate git-diff-files output for a know cache/work tree state.
git-diff-files >current && diff >/dev/null -b current expected
* FAIL 22: git-update-index --refresh should succeed.
git-update-index --refresh
* ok 23: no diff after checkout and git-update-index --refresh.
* failed 10 among 23 test(s)
-----
Any ideas on how to start tracking this one down?
Tim.
next reply other threads:[~2006-04-22 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 2:30 Tim O'Callaghan [this message]
2006-04-22 21:17 ` Problem with Git in Cygwin on x86-64 platform Alex Riesen
2006-04-23 0:57 ` Junio C Hamano
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=20060422023029.GC2444@Zangband \
--to=timo@dspsrv.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.