A lot of these failures are do to running as root (member of
Administrators). Using v1.6.3-rc4 (503f464...) I get:
make -i test
...
make aggregate-results
make[3]: Entering directory `/home/udslutz/BinMode/git/t'
'/bin/sh' ./aggregate-results.sh test-results/t*-*
fixed 3
success 4211
failed 5
broken 5
total 4272
make[3]: Leaving directory `/home/udslutz/BinMode/git/t'
...
-Don Slutz
-------- Original Message --------
Subject: Tests in Cygwin
From: Hannu Koivisto <azure@xxxxxx>
To: git@xxxxxxxxxxxxxxx
Date: 4/17/2009 5:47 AM
Greetings,
I upgraded to the latest git.git as of yesterday
(f800b65bea1504299747e7be03ee279508a74e1f) in Cygwin to see if it
still has the rebase and bogus modified files problem(s) (reported
earlier http://osdir.com/ml/git/2009-04/msg00619.html). It does;
I'll try to bisect it if I manage to make the test case automatic.
I also thought I'd run all the tests just for the heck of it. The
result is about 240 failures which are available here (lines
indicating passed tests removed):
http://www.iki.fi/azure/tmp/git-test-results-cygwin-f800b65bea1504299747e7be03ee279508a74e1f.txt
I wonder, since there seems to be some sort of mechanism to mark
failures "known" (at least I got a couple of "still broken ..."
lines), are all these unexpected, new problems, or is there perhaps
some separate list of known failures on Cygwin?
__________________________________________________________________________________________________________________
DISCLAIMER:"The information contained in this message and the attachments (if any) may be privileged and confidential and protected from disclosure. You are hereby notified that any unauthorized use, dissemination, distribution or copying of this communication, review, retransmission, or taking of any action based upon this information, by persons or entities other than the intended recipient, is strictly prohibited. If you are not the intended recipient or an employee or agent responsible for delivering this message, and have received this communication in error, please notify us immediately by replying to the message and kindly delete the original message, attachments, if any, and all its copies from your computer system. Thank you for your cooperation."
________________________________________________________________________________________________________________
--
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