From: Junio C Hamano <junkio@cox.net>
To: John Benes <smartcat99s@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: master has some toys
Date: Thu, 17 Nov 2005 19:36:24 -0800 [thread overview]
Message-ID: <7vfypur5jb.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <437D2D14.5080205@gmail.com> (John Benes's message of "Thu, 17 Nov 2005 19:23:32 -0600")
John Benes <smartcat99s@gmail.com> writes:
> Junio C Hamano wrote:
>
> I was able to compile master and pu on Cygwin without NO_MMAP=YesPlease
> in the Cygwin section. However, the make test failed on the
> binary-apply on both master and pu, output follows.
>
> Commit ID's used for testing:
> refs/heads/master 4e1da85d7d0480b6d9973317da4f7a5aa603fcb5
> refs/heads/pu 3b4587eb3c549649af7e84659b4808003c34c2d3
Thanks. But the test result look suspicious for pu.
$ git-ls-tree 3b4587eb t | grep t4103
outputs empty, so what you tested does not seem to be that
commit.
Anyway, the master is more important at this point.
> make test barfing on master:
> *** t4103-apply-binary.sh ***
> * FAIL 7: check binary diff with replacement.
> git-checkout master
> git-apply --check --allow-binary-replacement BF.diff
> * FAIL 8: check binary diff with replacement (copy).
> git-checkout master
> git-apply --check --allow-binary-replacement CF.diff
> * FAIL 15: apply binary diff.
> do_reset
> git-apply --allow-binary-replacement --index BF.diff &&
> test -z "$(git-diff --name-status binary)"
> * FAIL 16: apply binary diff (copy).
> do_reset
> git-apply --allow-binary-replacement --index CF.diff &&
> test -z "$(git-diff --name-status binary)"
> * failed 4 among 16 test(s)
> make[1]: *** [t4103-apply-binary.sh] Error 1
So it fails on these binary diffs with full index tests. Could
you try running it like this?
$ cd t
$ sh ./t4103-apply-binary.sh -i -v
If all things being equal, this will stop at the first failing
test "* FAIL 7: ", and you will have trash/ directory under t/.
$ cd trash
$ ls -l
I would first want to see if it was diff that failed or the
apply. What does BF.diff contain?
next prev parent reply other threads:[~2005-11-18 3:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 14:42 stgit truncates binary files to zero length when applying patches Karl Hasselström
2005-11-16 11:11 ` Catalin Marinas
2005-11-16 11:54 ` Karl Hasselström
2005-11-16 12:31 ` Catalin Marinas
2005-11-16 13:03 ` Karl Hasselström
2005-11-16 18:30 ` Junio C Hamano
2005-11-16 22:15 ` [PATCH] git-apply: fail if a patch cannot be applied Junio C Hamano
2005-11-17 1:21 ` master has some toys Junio C Hamano
2005-11-17 8:29 ` Alex Riesen
2005-11-17 10:12 ` Junio C Hamano
2005-11-17 10:36 ` Alex Riesen
2005-11-17 11:03 ` Junio C Hamano
2005-11-18 1:23 ` John Benes
2005-11-18 2:48 ` Johannes Schindelin
2005-11-18 4:01 ` John Benes
2005-11-18 3:36 ` Junio C Hamano [this message]
2005-11-18 3:49 ` A Large Angry SCM
2005-11-18 4:26 ` Junio C Hamano
2005-11-18 4:46 ` [PATCH] Deal with binary diff output from (unknown version of) diff Junio C Hamano
2005-11-18 4:58 ` A Large Angry SCM
2005-11-18 4:01 ` master has some toys John Benes
2005-11-18 4:27 ` Junio C Hamano
2005-11-18 4:35 ` John Benes
2005-11-18 4:40 ` A Large Angry SCM
2005-11-17 11:22 ` Johannes Schindelin
2005-11-17 11:08 ` Johannes Schindelin
2005-11-17 11:16 ` Junio C Hamano
2005-11-17 11:21 ` Alex Riesen
2005-11-17 11:51 ` Johannes Schindelin
2005-11-17 12:40 ` Alex Riesen
2005-11-17 19:29 ` Junio C Hamano
2005-11-17 23:36 ` Johannes Schindelin
2005-11-18 20:09 ` Junio C Hamano
2005-11-18 12:01 ` timo
2005-11-17 11:20 ` Alex Riesen
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=7vfypur5jb.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=smartcat99s@gmail.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).