From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: GIT Mailing-list <git@vger.kernel.org>
Subject: Test failures on cygwin (v1.6.0)
Date: Tue, 26 Aug 2008 18:41:50 +0100 [thread overview]
Message-ID: <48B4405E.2020507@ramsay1.demon.co.uk> (raw)
Hi *,
Having upgraded to v1.6.0, via tar-ball as usual, I must note a new
"make test" failure, namely t9700-perl-git.sh. In order to pass, I
need to run:
GIT_SKIP_TESTS='t0004 t3700.2[1234] t9700' make test
I haven't had time to look into the new failure yet; I'll report back
when I know more. (I will send a couple of minor patches related to
the 1.6.0 build)
Also, the new test summary shows (on Linux and cygwin):
Linux Cygwin
fixed 1 3
success 3748 3511
failed 0 0
broken 2 2
total 3751 3520
[time: 5m47s 47m]
Note the number of fixed on cygwin. It took some time to find, but it
appears that the additional FIXED where t0050-filsystem.sh tests
5 "merge (case change)" and 6 "add (with different case)". Again, I
haven't investigated yet.
ATB,
Ramsay Jones
next reply other threads:[~2008-08-26 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 17:41 Ramsay Jones [this message]
2008-08-27 6:12 ` Test failures on cygwin (v1.6.0) Alex Riesen
2008-08-28 15:46 ` Ramsay Jones
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=48B4405E.2020507@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--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 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).