git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: 1.7.2 cycle will open soon
Date: Thu, 6 May 2010 03:49:43 -0400	[thread overview]
Message-ID: <20100506074943.GA24399@coredump.intra.peff.net> (raw)
In-Reply-To: <4BE26A83.4010708@viscovery.net>

On Thu, May 06, 2010 at 09:06:43AM +0200, Johannes Sixt wrote:

> Am 5/6/2010 8:44, schrieb Jonathan Nieder:
> >  test_when_finished () {
> > 	test_cleanup="$* && $test_cleanup"
> >  }
> 
> I'm wondering why you want this test_cleanup at all?
> 
> Is it so that subsequent tests can succeed even if an earlier test failed
> before its regular cleanup?
> 
> I don't see what this buys you. If a test case uncovers a regression, you
> got to fix it - who cares how many later tests fail or not? Once you are
> finished with your change, all tests will pass anyway (including their
> regular cleanups).

I have to agree. Yes, using test_when_finished can make _some_ tests
more robust, but there will still be many tests whose breakage will
break future tests. And many of those will never be fixed, because the
tests simply build on one another.

So I don't think we will ever "solve" this problem, which means testers
will continue to have to fix early failures before looking at later
ones, because they don't know if the later test is a false negative or
not. And as you point out, it is simply not that big a deal in the first
place.

-Peff

  reply	other threads:[~2010-05-06  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05  5:39 1.7.2 cycle will open soon Junio C Hamano
2010-05-06  5:52 ` Jeff King
2010-05-06  6:44   ` Jonathan Nieder
2010-05-06  6:54     ` Jeff King
2010-05-06  8:41       ` [PATCH] test-lib: some shells do not let $? propagate into an eval Jonathan Nieder
2010-05-06  8:57         ` Jeff King
2010-05-06 20:20           ` Junio C Hamano
2010-05-06  7:06     ` 1.7.2 cycle will open soon Johannes Sixt
2010-05-06  7:49       ` Jeff King [this message]
2010-05-06  8:01       ` Jonathan Nieder
2010-05-06  6:57   ` Johannes Sixt

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=20100506074943.GA24399@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    --cc=jrnieder@gmail.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).