From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
git@vger.kernel.org
Subject: [test failure] Re: t4114 binary file becomes symlink
Date: Sat, 18 Jul 2009 22:39:22 +0200 [thread overview]
Message-ID: <20090718203922.GG16708@vidovic> (raw)
In-Reply-To: <7veisd3k31.fsf@alter.siamese.dyndns.org>
The 18/07/09, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > Are you compiling with any special options?
Normally, no (cf. my mail to Johannes Sixt).
> > I usually compile with just
> > "-g -Wall -Werror", but I also tried with "-O2" and couldn't reproduce.
The Makefile have
215:CFLAGS = -g -O2 -Wall
217:ALL_CFLAGS = $(CFLAGS)
and it should be OK. I know that -Werror will fail on
libgit.a(mkdtemp.o): In function `gitmkdtemp':
/home/nicolas/dev/official_packages/git/compat/mkdtemp.c:5: warning: the
use of `mktemp' is dangerous, better use `mkstemp'
but I think this is an unrelated problem.
$ gcc --version
gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.3)
> Me neither, but I found an unrelated anomaly in the output from the test
> nearby.
>
> Switched to branch 'foo-baz-renamed-from-foo'
> * ok 3: file renamed from foo/baz to foo
>
> * expecting success:
> git checkout -f foo-becomes-a-directory &&
> git diff-tree -p HEAD initial > patch &&
> git apply --index < patch
>
> error: Invalid path ''
> Switched to branch 'foo-becomes-a-directory'
> * ok 4: directory becomes file
>
> Notice the "error"?
I couldn't reproduce this error here with
sh t4114-apply-typechange.sh --verbose
and
sh t4114-apply-typechange.sh --verbose --debug
on the current next.
With this patch, I still fail on the test.
--
Nicolas Sebrecht
next prev parent reply other threads:[~2009-07-18 20:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 13:45 [test failure] t4114 binary file becomes symlink Nicolas Sebrecht
2009-07-18 13:56 ` Jeff King
2009-07-18 14:16 ` [test failure] " Nicolas Sebrecht
2009-07-18 15:31 ` Jeff King
2009-07-18 18:46 ` Junio C Hamano
2009-07-18 20:39 ` Nicolas Sebrecht [this message]
2009-07-18 23:18 ` Linus Torvalds
2009-07-18 19:06 ` Johannes Sixt
2009-07-18 20:17 ` Nicolas Sebrecht
2009-07-18 21:13 ` Nicolas Sebrecht
2009-07-19 10:33 ` ./configure misdetects SNPRINTF_RETURNS_BOGUS (was: [test failure] t4114 binary file becomes symlink) Jakub Narebski
2009-07-19 12:48 ` [PATCH] configure: use AC_SEARCH_LIBS instead of AC_CHECK_LIB Nicolas Sebrecht
2009-07-19 13:14 ` [PATCH] " Nicolas Sebrecht
2009-07-19 16:13 ` Junio C Hamano
2009-07-19 22:53 ` Eric Blake
2009-07-21 15:04 ` [PATCH] " Brandon Casey
2009-07-21 15:12 ` Brandon Casey
2009-07-21 15:20 ` Paolo Bonzini
2009-07-21 15:34 ` Brandon Casey
2009-07-21 20:23 ` [PATCH] configure.ac: rework/fix the NEEDS_RESOLV and NEEDS_LIBGEN tests Brandon Casey
2009-07-21 20:33 ` Junio C Hamano
2009-07-22 14:59 ` Brandon Casey
2009-07-22 22:15 ` [PATCH] config.mak.in: continue fixing NEEDS_LIBGEN autoconfigure feature Brandon Casey
2009-07-22 22:35 ` Junio C Hamano
2009-07-23 16:22 ` Brandon Casey
2009-07-18 22:03 ` [test failure] Re: t4114 binary file becomes symlink Johannes Sixt
2009-07-18 22:29 ` Jeff King
2009-07-18 22:51 ` Nicolas Sebrecht
2009-07-19 11:01 ` Johannes Sixt
2009-07-20 9:09 ` Jeff King
2009-07-20 20:51 ` Johannes Sixt
2009-07-20 21:56 ` Linus Torvalds
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=20090718203922.GG16708@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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.