Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of randall.leeds@gmail.com
 designates 209.85.213.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+Y+444tsghWvxV0=xjX3SUNvXgacn3VzWP=mQHs-wmj0ukcGQ@mail.gmail.com>
References: <20111031083756.4B8E65496F@tyr.zones.apache.org>
	<CAJ_m3YBOWUWcCuKrDQiqESR-pFfzx8FV8P94GF2nkaoVkMURxg@mail.gmail.com>
	<CA+Y+444tsghWvxV0=xjX3SUNvXgacn3VzWP=mQHs-wmj0ukcGQ@mail.gmail.com>
Date: Thu, 10 Nov 2011 18:20:06 -0800
Message-ID: 
 <CAAL6JQi9jRR+BW+1CWooMggTcC+AQrVOaAwEaHk3NbrdO-bz5Q@mail.gmail.com>
Subject: Re: git commit: Start/Stop CouchDB aronud JS CLI tests.
From: Randall Leeds <randall.leeds@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

Can someone turn this into a ticket?

Sounds like we need port=0 and a trap command.

Also, I noticed that running the tests directly seems to start/stop
the server but make check doesn't? Is that correct?

On Mon, Oct 31, 2011 at 11:16, Noah Slater <nslater@tumbolia.org> wrote:
> On Mon, Oct 31, 2011 at 2:38 PM, Paul Davis <paul.joseph.davis@gmail.com>wrote:
>
> Before I forget, there's also a nifty trap command thing in case its
>> killed by a signal. There's an example of its use here:
>>
>>
>> https://svn.apache.org/repos/infra/infrastructure/trunk/projects/git/bin/update-mirror.sh
>>
>> Not sure how portable that is, but it seems like something we might
>> want to look into to be extra sure that the node comes down.
>>
>
> +1
>
> The trap command should be quite portable.
>