From: "Amir E. Aharoni" <amir.aharoni@mail.huji.ac.il>
To: git@vger.kernel.org
Subject: tests failing on Cygwin
Date: Sun, 8 Aug 2010 00:37:00 +0300 [thread overview]
Message-ID: <AANLkTimeE-dJrSrjJSuP9Zm93tF9woNakO+HwspJg6CZ@mail.gmail.com> (raw)
Hallo,
I couldn't find a better place to report this and i don't know whether
anyone really cares about this, but i'll try anyway.
I want to make a few corrections to the core documentation. I cloned
git.git and before starting the actual i built it and ran `make test',
just in case, and some tests failed.
I am doing this on XP/Cygwin. Some of them may be irrelevant for
Cygwin; if so, they probably should be skipped. And maybe i am just
misunderstanding something.
Here's the list of files and names of failed tests:
t0001-init.sh:
* init notices EPERM
t1004-read-tree-m-u-wf.sh:
* funny symlink in work tree, un-unlink-able
t3300-funny-names.sh:
* git diff-tree delete with-funny
* ... and all the test from here until the end of that file
t3301-notes.sh:
* test_expect_success 'git notes copy --for-rewrite (disabled)' '
git config notes.rewrite.bar false &&
echo $(git rev-parse HEAD~3) $(git rev-parse HEAD) |
git notes copy --for-rewrite=bar &&
git log -2 > output &&
test_cmp expect output
'
t556x_common:
* direct refs/heads/master not found
* no export by default
* static file if http.getanyfile true is ok
* http.uploadpack false
* http.receivepack default disabled
* http.receivepack false
t7300-clean.sh:
* removal failure
t7606-merge-custom.sh:
* merge c2 with a custom strategy
--
אָמִיר אֱלִישָׁע אַהֲרוֹנִי
Amir Elisha Aharoni
http://aharoni.wordpress.com
"We're living in pieces,
I want to live in peace." - T. Moore
next reply other threads:[~2010-08-07 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 21:37 Amir E. Aharoni [this message]
2010-08-07 23:02 ` tests failing on Cygwin Ævar Arnfjörð Bjarmason
2010-08-07 23:04 ` Ævar Arnfjörð Bjarmason
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=AANLkTimeE-dJrSrjJSuP9Zm93tF9woNakO+HwspJg6CZ@mail.gmail.com \
--to=amir.aharoni@mail.huji.ac.il \
--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).