From: David Fang <fang@csl.cornell.edu>
To: git@vger.kernel.org
Subject: git test failure: t9903-bash-prompt.sh on darwin8
Date: Mon, 28 Oct 2013 19:11:35 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1310281859460.5295@hal-00.csl.cornell.edu> (raw)
Hi,
I'm seeing a test failure with git-1.8.4 on powerpc-darwin8:
[11:00:56] t9903-bash-prompt.sh ...............................
not ok 13 - prompt - interactive rebase
not ok 14 - prompt - rebase merge
Details here:
http://paste.lisp.org/display/139525
The odd thing is that when I run the test t9903 interactively,
post-mortem, it passes -- I am unable to reproduce the failure outside of
the unprivileged build environment.
Interactively, the test always passes regardless of my interaction shell:
csh, sh-2.0, bash-4.2. (Noninteractive test happens to use bash-2.0.)
So I force the test to halt immediately upon failure to examine the
temporary trash directory, and the difference between actual/expected:
http://paste.lisp.org/display/139525#4
What could cause the results to differ between by interactive and
non-interactive testing of t9903? Is there a real problem?
Fang
--
David Fang
http://www.csl.cornell.edu/~fang/
reply other threads:[~2013-10-28 23:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.1310281859460.5295@hal-00.csl.cornell.edu \
--to=fang@csl.cornell.edu \
--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).