From: Mike Ralphson <mike.ralphson@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: t3702-add-edit.sh failure in next
Date: Mon, 27 Apr 2009 16:12:15 +0100 [thread overview]
Message-ID: <e2b179460904270812t3fa159f1ja3b06905d9effebe@mail.gmail.com> (raw)
I'm seeing a reproducible failure in t3702 on AIX 5.3, shell set to
bash (v2.05b)
The 'test_cmp orig-patch expected-patch' is seeing this diff:
2c2
< index b9834b5..52aff4c 100644
---
> index b9834b5..0b8f197 100644
The index seems to contain the expected content.
I've tried to eliminate GIT* environment variables which might be
affecting the commit id, and tried adding extra test_ticks, but I'm
afraid I can't work out what's up here.
Normally all tests pass fine with the exception of some skipped
because of known iconv issues on this platform.
Mike
next reply other threads:[~2009-04-27 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 15:12 Mike Ralphson [this message]
2009-04-27 16:13 ` t3702-add-edit.sh failure in next Johannes Schindelin
2009-04-27 16:30 ` Mike Ralphson
2009-04-27 17:51 ` [PATCH] t3702: fix reliance on SHELL_PATH being '/bin/sh' Johannes Schindelin
2009-04-27 18:01 ` Mike Ralphson
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=e2b179460904270812t3fa159f1ja3b06905d9effebe@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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).