From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 0/3] Enable parallelized tests
Date: Fri, 8 Aug 2008 17:36:24 +0200 [thread overview]
Message-ID: <20080808153624.GA28716@neumann> (raw)
In-Reply-To: <alpine.DEB.1.00.0808080752210.9611@pacific.mpi-cbg.de.mpi-cbg.de>
Hi,
On Fri, Aug 08, 2008 at 07:59:08AM +0200, Johannes Schindelin wrote:
> This patch pair enables parallel tests.
Glad to see that others have also picked up this topic. I have also
written parallel testing patches back in March, but did not send them
out, as there were issues I could not resolve in a satisfactory way -
and your patches doesn't seem to address theim either.
There are a few tests involving http transfers, namely:
t5540-http-push.sh
t9115-git-svn-dcommit-funky-renames.sh
t9118-git-svn-funky-branch-names.sh
t9120-git-svn-clone-with-percent-escapes.sh
These start an apache web server at the beginning of the test and shut
it down after the test finished. Obviously, if you run tests in
parallel then these tests can also run concurrently. The problem is
with the svn tests, as all those tests use the same directory and port
for the web server, resulting in failed tests with -jN.
t5540 is not an issue at the moment, as it uses lib-httpd.sh, hence a
different directory and a (possibly) different port than the svn
tests. However, who knows, in the future we might have other tests
using lib-httpd.sh.
The simplest solution would be to disable parallel testing altogether
if http tests are enabled (GIT_TEST_HTTPD and SVN_HTTPD_PORT). But
IMHO it would be much better to have only one apache process for the
_whole_ testsuite, and to have different paths for the test repos
under its documentroot. But yes, it's more difficult to implement; at
least I could not do it.
Regards,
Gábor
next prev parent reply other threads:[~2008-08-08 15:37 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
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 ` SZEDER Gábor [this message]
2008-08-08 16:02 ` [PATCH 0/3] Enable parallelized tests 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=20080808153624.GA28716@neumann \
--to=szeder@ira.uka.de \
--cc=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).