From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/5] Add test for sanitized work-tree behaviour
Date: Thu, 26 Jul 2007 15:05:23 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707261503530.14781@racer.site> (raw)
In-Reply-To: <7vfy3b8wkp.fsf@assigned-by-dhcp.cox.net>
Hi,
On Thu, 26 Jul 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> > ---
> > ...
> > @@ -3,90 +3,109 @@
> > test_description='test separate work tree'
> > . ./test-lib.sh
> >
> > +i=1
> > +
> > test_rev_parse() {
> > - ...
> > + name="$1"
> > + for option in --is-bare-repository --is-inside-git-dir \
> > + --is-inside-work-tree --show-prefix
> > + do
> > + shift
> > + test_expect_success "$name: $option" \
> > + "test '$1' = \"\$(git rev-parse $option)\""
>
> > +i=$(($i+1))
> > +test $i = $STOPI && gdb --args git rev-parse $option
>
> Eh?
Yes, got me there. It was a real PITA to debug that thing, given that the
tests were written in the spirit of Malbolge. So the easiest method to
debug it was for me to "-i -v" the test, run it again with "STOPI=$n ..
-v", and work out what was the intended behaviour, and whether to fix the
test or the logic.
Will clean up.
Ciao,
Dscho
prev parent reply other threads:[~2007-07-26 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 6:32 [PATCH 4/5] Add test for sanitized work-tree behaviour Johannes Schindelin
2007-07-26 7:15 ` Junio C Hamano
2007-07-26 14:05 ` Johannes Schindelin [this message]
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.0707261503530.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).