From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "SZEDER Gábor" <szeder@ira.uka.de>,
git@vger.kernel.org, gitster@pobox.com,
"Sverre Rabbelier" <alturin@gmail.com>
Subject: Re: [PATCH] test-lib: write test results to test-results/<basename>-<pid>
Date: Sat, 14 Mar 2009 13:16:17 +0100 [thread overview]
Message-ID: <20090314121617.GJ6808@neumann> (raw)
In-Reply-To: <alpine.DEB.1.00.0903141250450.10279@pacific.mpi-cbg.de>
Hi,
On Sat, Mar 14, 2009 at 12:53:06PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Fri, 13 Mar 2009, SZEDER Gábor wrote:
>
> > diff --git a/t/Makefile b/t/Makefile
> > index 0d65ced..2e6e205 100644
> > --- a/t/Makefile
> > +++ b/t/Makefile
> > @@ -14,14 +14,11 @@ SHELL_PATH_SQ = $(subst ','\'',$(SHELL_PATH))
> > T = $(wildcard t[0-9][0-9][0-9][0-9]-*.sh)
> > TSVN = $(wildcard t91[0-9][0-9]-*.sh)
> >
> > -all: pre-clean $(T) aggregate-results clean
> > +all: $(T) aggregate-results clean
Well, this part is wrong, or at least not up-to-date. I just digged
up an ancient branch in my tree and sent out the diff, without
realizing that there were some conflicting changes since then.
> >
> > $(T):
> > @echo "*** $@ ***"; GIT_CONFIG=.git/config '$(SHELL_PATH_SQ)' $@ $(GIT_TEST_OPTS)
> >
> > -pre-clean:
> > - $(RM) -r test-results
> > -
> > clean:
> > $(RM) -r 'trash directory' test-results
> >
> > @@ -33,5 +30,5 @@ full-svn-test:
> > $(MAKE) $(TSVN) GIT_SVN_NO_OPTIMIZE_COMMITS=1 LC_ALL=C
> > $(MAKE) $(TSVN) GIT_SVN_NO_OPTIMIZE_COMMITS=0 LC_ALL=en_US.UTF-8
> >
> > -.PHONY: pre-clean $(T) aggregate-results clean
> > +.PHONY: $(T) aggregate-results clean
> > .NOTPARALLEL:
>
> This is wrong. If you have failing tests, or if you interrupt the tests,
> it will never clean the test results, and after Hannes' patch you _will_
> have stale files lying around all the time.
If you have failing tests, or if you interrupt the tests, then you
will have stale files lying around _anyway_: not only test results
are left there, but also trash directories. To remove the trash
directories, you'll need to run 'make clean' (in t/), but that will
remove the test results, too, so there is no difference. But even if
you don't run 'make clean' before running the test suite again, test
results cruft from the previous run doesn't matter, because they will
be overwritten.
Best,
Gábor
next prev parent reply other threads:[~2009-03-14 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1236961524u.git.johannes.schindelin@gmx.de>
2009-03-13 16:26 ` [PATCH] test-lib: write test results to test-results/<basename>-<pid> Johannes Schindelin
2009-03-13 16:36 ` Johannes Schindelin
2009-03-13 17:20 ` SZEDER Gábor
2009-03-13 17:44 ` SZEDER Gábor
2009-03-14 11:53 ` Johannes Schindelin
2009-03-14 12:16 ` SZEDER Gábor [this message]
2009-03-14 12:22 ` Johannes Schindelin
2009-03-14 12:28 ` SZEDER Gábor
2009-03-14 13:16 ` Sverre Rabbelier
2009-03-14 13:59 ` SZEDER Gábor
2009-03-16 10:18 ` Johannes Schindelin
2009-03-16 10:41 ` SZEDER Gábor
2009-03-13 17:20 ` Junio C Hamano
2009-03-13 17:22 ` Junio C Hamano
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=20090314121617.GJ6808@neumann \
--to=szeder@ira.uka.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=alturin@gmail.com \
--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).