git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Clemens Buchacher <drizzd@aon.at>
Cc: Mike Hommey <mh@glandium.org>, Eric Wong <normalperson@yhbt.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH] http-push: add regression tests
Date: Mon, 25 Feb 2008 16:24:30 -0800	[thread overview]
Message-ID: <7vprukfttt.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080225232820.GA18254@localhost> (Clemens Buchacher's message of "Tue, 26 Feb 2008 00:28:20 +0100")

Clemens Buchacher <drizzd@aon.at> writes:

> http-push tests require a web server with WebDAV support.

I'd rather see these tests that are heavyweight and (more
importantly) open a listened network ports kept strictly
optional.  IOW, please enable them only when the user asks for
them, like some of the heavier GIT_SVN tests already do with
"make full-svn-test" target.

>  create mode 100644 t/lib-httpd.sh
>  create mode 100644 t/lib-httpd/apache.conf
>  create mode 100644 t/lib-httpd/ssl.cnf
>  create mode 100644 t/t5540-http-push.sh

Others are Ok but the last one should be 100755 per convention.

> +TEST_PATH="$PWD"/../lib-httpd
> +HTTPD_ROOT_PATH="$PWD"/httpd
> +HTTPD_DOCUMENT_ROOT_PATH="$PWD"/httpd/www
> +
> +if ! test -x "$LIB_HTTPD_PATH"
> +then
> +        say_color "" "skipping test, no web server found at $LIB_HTTPD_PATH"

Just use "say" to let "say" function pick the color.

> +	if test "$LIB_HTTPD_DAV" != "" -o "$LIB_HTTPD_SVN" != ""
> +	then
> +		HTTPD_PARA="$HTTPD_PARA -DDAV"
> +
> +		if test "$LIB_HTTPD_SVN" != ""
> +		then
> +			HTTPD_PARA="$HTTPD_PARA -DSVN"
> +			rawsvnrepo="$HTTPD_ROOT_PATH/svnrepo"
> +			svnrepo="http://127.0.0.1:$LIB_HTTPD_PORT/svn"

Subversion???  Ah, you are preparing for enhancement of t91XX series?

> +		fi
> +	fi
> +}
> +
> +start_httpd() {
> +	prepare_httpd
> +
> +	"$LIB_HTTPD_PATH" $HTTPD_PARA \
> +		-c "Listen 127.0.0.1:$LIB_HTTPD_PORT" -k start
> +}
> +
> +stop_httpd() {
> +	"$LIB_HTTPD_PATH" $HTTPD_PARA -k stop
> +}

I have to wonder where it is arranged so that a test failure
(including ^C out of it, or losing SSH connection to the
terminal) would cause the server to be killed off.

  reply	other threads:[~2008-02-26  0:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 13:07 [PATCH] http-push: Fix error message for push <remote> :<branch> Clemens Buchacher
2008-02-18 13:45 ` Johannes Schindelin
2008-02-18 15:55   ` [PATCH] http-push: push <remote> :<branch> deletes remote branch Clemens Buchacher
2008-02-18 16:44     ` Clemens Buchacher
2008-02-18 17:35       ` Johannes Schindelin
2008-02-18 17:34     ` Johannes Schindelin
2008-02-19 12:58       ` Clemens Buchacher
2008-02-19 13:17         ` Johannes Schindelin
2008-02-19 13:24           ` Mike Hommey
2008-02-19 13:31             ` Johannes Schindelin
2008-02-19 21:35               ` Junio C Hamano
2008-02-19 22:25                 ` Johannes Schindelin
2008-02-23 21:28       ` [PATCH] http-push: add regression tests Clemens Buchacher
2008-02-24  8:58         ` Mike Hommey
2008-02-24 18:03           ` Clemens Buchacher
2008-02-24 18:48             ` Mike Hommey
2008-02-24 19:14               ` Clemens Buchacher
2008-02-25 23:28               ` Clemens Buchacher
2008-02-26  0:24                 ` Junio C Hamano [this message]
2008-02-27  8:54                   ` Clemens Buchacher
2008-02-27  9:16                     ` Mike Hommey
2008-02-27  9:51                     ` Johannes Schindelin
2008-02-27 19:23                       ` Clemens Buchacher
2008-02-27 19:27                         ` [PATCH 1/2] http-push: push <remote> :<branch> deletes remote branch Clemens Buchacher
2008-02-27 19:28                         ` [PATCH 2/2] http-push: add regression tests Clemens Buchacher
2008-02-27 22:24                         ` [PATCH] " Johannes Schindelin
2008-02-26 19:32                 ` Mike Hommey

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=7vprukfttt.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=drizzd@aon.at \
    --cc=git@vger.kernel.org \
    --cc=mh@glandium.org \
    --cc=normalperson@yhbt.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 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).