All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Aneesh Kumar" <aneesh.kumar@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Test fails on ubuntu breezy
Date: Sat, 15 Apr 2006 00:24:44 -0700	[thread overview]
Message-ID: <7vbqv3jo77.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: cc723f590604142347p7646aa40r52506a0d85b7d817@mail.gmail.com

"Aneesh Kumar" <aneesh.kumar@gmail.com> writes:

> I am still having failure with the top of the tree. I guess it is
> because git rm exit with status 0.

Please don't guess, but validate (I know you are capable of
doing so).

What I would do to see what is happening would be to do
something like the attached patch and re-run the test.

BTW, you did "sh -x t3600-rm.sh" which is very good.  I usually
do it when debugging hard-to-debug testsuite problem, especially
ones which I do not know intimately, written by somebody else,
like this:

	sh -x tXXXX-that-test.sh -i

The -i option makes it immediately stop at the first test failure.

-- >8 --
diff --git a/git-rm.sh b/git-rm.sh
index fda4541..622ffca 100755
--- a/git-rm.sh
+++ b/git-rm.sh
@@ -43,6 +43,8 @@ case "$#" in
 	;;
 esac
 
+set -x
+
 if test -f "$GIT_DIR/info/exclude"
 then
 	git-ls-files -z \

  reply	other threads:[~2006-04-15  7:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 11:54 Test fails on ubuntu breezy linux
2006-04-13 18:56 ` Junio C Hamano
2006-04-15  6:47   ` Aneesh Kumar
2006-04-15  7:24     ` Junio C Hamano [this message]
2006-04-15 15:43       ` Aneesh Kumar
2006-04-15  7:33     ` Aneesh Kumar
  -- strict thread matches above, loose matches on Subject: below --
2006-04-13  7:53 Aneesh Kumar
2006-04-13 10:20 ` Peter Eriksen

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=7vbqv3jo77.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=aneesh.kumar@gmail.com \
    --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 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.