All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2008, #06; Wed, 20)
Date: Wed, 20 Aug 2008 19:30:54 -0700	[thread overview]
Message-ID: <7vy72rkskh.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080821011811.GA13915@coredump.intra.peff.net> (Jeff King's message of "Wed, 20 Aug 2008 21:18:11 -0400")

Jeff King <peff@peff.net> writes:

> I really liked this the first time I ran "make -j4 test". However, it
> now cleans up the trash directory automagically after a successful run.
> This bit me today when I added a test that should have failed but
> accidentally passed. I wanted to look at the output, but it was gone.
>
> Probably it's not worth worrying about, since that is certainly the less
> common case, and I can work around it by editing the passing test script
> to provoke failure.

When I add to an existing test, I usually:

 * guess where I want to start the new test;
 * insert an "exit" there to cause failure;
 * run it and inspect the state of the test directory;
 * write the new test just before the "exit";
 * run it until I like the new test;
 * remove the "exit".

  reply	other threads:[~2008-08-21  2:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  0:30 What's cooking in git.git (Aug 2008, #06; Wed, 20) Junio C Hamano
2008-08-21  1:18 ` Jeff King
2008-08-21  2:30   ` Junio C Hamano [this message]
2008-08-21  7:49   ` [PATCH] test-lib: do not remove trash_directory if called with --debug Johannes Schindelin
2008-08-21  8:52     ` Junio C Hamano
2008-08-21 12:55       ` Jeff King
2008-08-21 12:10 ` What's cooking in git.git (Aug 2008, #06; Wed, 20) Michael J Gruber

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=7vy72rkskh.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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.