From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 3/3] Enable parallel tests
Date: Thu, 07 Aug 2008 23:52:25 -0700 [thread overview]
Message-ID: <7vvdycf17a.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0808080754230.9611@pacific.mpi-cbg.de.mpi-cbg.de> (Johannes Schindelin's message of "Fri, 8 Aug 2008 07:59:23 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On multiprocessor machines, or with I/O heavy tests (that leave the
> CPU waiting a lot), it makes sense to parallelize the tests.
I was actually thinking about doing this eventually. Thanks for beating
me to it.
> Parallel mode also triggers removal of the trash directory in the test
> itself if everything went fine, so that the trash directories do not
> pile up only to be removed at the very end.
I think making the tests remove their own mess makes sense regardless.
I have to wonder why you would want to make this change conditional on
MAKEFLAGS. I was envisioning that parallel tests would run in "trash
directory/$(basename $0)" or something.
Are there downsides of doing this change unconditionally?
> clean:
> - $(RM) -r 'trash directory' test-results
> + $(RM) -rf 'trash directory' test-results
This is not needed, I think, as RM is defined with -f already.
next prev parent reply other threads:[~2008-08-08 6:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 5:59 [PATCH 0/3] Enable parallelized tests Johannes Schindelin
2008-08-08 5:59 ` [PATCH 1/3] t9700: remove useless check Johannes Schindelin
2008-08-08 5:59 ` [PATCH 2/3] tests: Clarify dependencies between tests, 'aggregate-results' and 'clean' Johannes Schindelin
2008-08-08 5:59 ` [PATCH 3/3] Enable parallel tests Johannes Schindelin
2008-08-08 6:52 ` Junio C Hamano [this message]
2008-08-08 10:26 ` Johannes Schindelin
2008-08-08 10:33 ` Junio C Hamano
2008-08-08 7:44 ` René Scharfe
2008-08-08 8:28 ` Junio C Hamano
2008-08-08 9:31 ` [PATCH] tests: use $TEST_DIRECTORY to refer to the t/ directory Junio C Hamano
2008-08-08 10:35 ` Johannes Schindelin
2008-08-08 10:40 ` Junio C Hamano
2008-08-08 14:40 ` Stephan Beyer
2008-08-09 22:53 ` Olivier Marin
2008-08-09 23:20 ` Junio C Hamano
2008-08-10 7:33 ` Junio C Hamano
2008-08-08 10:37 ` [PATCH 3/3] Enable parallel tests Johannes Schindelin
2008-08-08 11:08 ` [PATCH 3/3 v2] " Johannes Schindelin
2008-08-08 15:03 ` Stephan Beyer
2008-08-08 15:27 ` Johannes Schindelin
2008-08-08 15:36 ` [PATCH 0/3] Enable parallelized tests SZEDER Gábor
2008-08-08 16:02 ` Stephan Beyer
2008-08-08 16:30 ` Johannes Schindelin
2008-08-08 16:33 ` Stephan Beyer
2008-08-08 16:51 ` Johannes Schindelin
2008-08-08 16:56 ` Stephan Beyer
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=7vvdycf17a.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--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.